diff --git a/doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml b/doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml
index 0aaab469d1..a7f7c88d29 100644
--- a/doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml
+++ b/doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml
@@ -45,7 +45,7 @@
         more than one compute resource pool. Each independent resource
         pool should be designed to provide service for specific
         flavors of instances or groupings of flavors. For the purpose
-        of this book, "instance" refers to a virtual machines and the
+        of this book, "instance" refers to a virtual machine and the
         operating system running on the virtual machine. Designing
         multiple resource pools helps to ensure that, as instances are
         scheduled onto compute hypervisors, each independent node's
@@ -92,7 +92,7 @@
         in the cloud.</para>
     <para>In addition to the impact on actual compute services, it is
         also important to consider the compute requirements of
-        resource nodes within the cloud. Resource nodes refers to
+        resource nodes within the cloud. Resource nodes refer to
         non-hypervisor nodes providing controller, object storage,
         block storage, or networking services in the cloud. The number
         of processor cores and threads has a direct correlation to the
@@ -128,7 +128,7 @@
         protect sensitive data and also protects against unauthorized
         access to services.</para>
     <para>Based on the requirements of instances being serviced in the
-        cloud, the next design choice which will affect your design is
+        cloud, the next design choice, which will affect your design is
         the choice of network service which will be used to service
         instances in the cloud. The choice between legacy networking (nova-network), as a
         part of OpenStack Compute, and OpenStack Networking
@@ -565,8 +565,8 @@
         usage increases.</para></section>
     <section xml:id="storage-performance-tech-considerations">
       <title>Storage performance</title>
-    <para>When considering performance of OpenStack Block Storage,
-        hardware and architecture choice is important. Block Storage
+    <para>When considering the performance of OpenStack Block Storage,
+        hardware and architecture choices are important. Block Storage
         can use enterprise back-end systems such as NetApp or EMC, use
         scale out storage such as GlusterFS and Ceph, or simply use
         the capabilities of directly attached storage in the nodes
@@ -751,7 +751,7 @@
         the API services behind hardware that performs SSL termination
         is strongly recommended.</para>
     <para>
-      For more information OpenStack Security, see the <link
+      For more information on OpenStack Security, see the <link
       xlink:href="http://docs.openstack.org/security-guide/"><citetitle>OpenStack
       Security Guide</citetitle></link>
     </para>