diff --git a/doc/common/section_objectstorage-arch.xml b/doc/common/section_objectstorage-arch.xml
index f0077c624a..aab98cf9b2 100644
--- a/doc/common/section_objectstorage-arch.xml
+++ b/doc/common/section_objectstorage-arch.xml
@@ -58,7 +58,7 @@
             </imageobject>
         </mediaobject>
     </figure>
-        <para>Currently, 2TB or 3TB SATA disks deliver good price/performance value. You can use
+        <para>Currently, 2 TB or 3 TB SATA disks deliver good price/performance value. You can use
             desktop-grade drives if you have responsive remote hands in the datacenter and
             enterprise-grade drives if you don't.</para>
     <section xml:id="section_storage-nodes-considerations">
diff --git a/doc/common/section_storage-concepts.xml b/doc/common/section_storage-concepts.xml
index bf794da861..dc4ac21a71 100644
--- a/doc/common/section_storage-concepts.xml
+++ b/doc/common/section_storage-concepts.xml
@@ -48,8 +48,8 @@
         <td>Easily scalable for future growth</td>
       </tr>
       <tr>
-        <td>Example: 10GB first disk, 30GB/core second disk</td>
-        <td>Example: 1TB "extra hard drive"</td>
+        <td>Example: 10 GB first disk, 30 GB/core second disk</td>
+        <td>Example: 1 TB "extra hard drive"</td>
         <td>Example: 10s of TBs of data set storage</td>
       </tr>
     </tbody>
diff --git a/doc/config-reference/compute/section_compute-scheduler.xml b/doc/config-reference/compute/section_compute-scheduler.xml
index a92b0a2ef1..85d1bfa967 100644
--- a/doc/config-reference/compute/section_compute-scheduler.xml
+++ b/doc/config-reference/compute/section_compute-scheduler.xml
@@ -412,8 +412,8 @@ isolated_images=342b492c-128f-4a42-8d3a-c5088cf27d13,ebd267a6-ca86-4d6c-9a0e-bd1
                 <filename>nova.conf</filename>. The default setting
                 is:</para>
             <programlisting language="ini">ram_allocation_ratio=1.5</programlisting>
-            <para>With this setting, if there is 1GB of free RAM, the
-                scheduler allows instances up to size 1.5GB to be run
+            <para>With this setting, if there is 1 GB of free RAM, the
+                scheduler allows instances up to size 1.5 GB to be run
                 on that instance.</para>
         </section>
         <section xml:id="retryfilter">
diff --git a/doc/training-guides/module003-ch007-swift-cluster-architecture.xml b/doc/training-guides/module003-ch007-swift-cluster-architecture.xml
index 7030aa6a9c..43f2bfb7f7 100644
--- a/doc/training-guides/module003-ch007-swift-cluster-architecture.xml
+++ b/doc/training-guides/module003-ch007-swift-cluster-architecture.xml
@@ -69,7 +69,7 @@
             provisioned with single gigabit or 10 gigabit network
             interface depending on expected workload and desired
             performance.</para>
-        <para>Currently 2TB or 3TB SATA disks deliver good
+        <para>Currently 2 TB or 3 TB SATA disks deliver good
             price/performance value. Desktop-grade drives can be used
             where there are responsive remote hands in the datacenter,
             and enterprise-grade drives can be used where this is not
@@ -86,4 +86,4 @@
                 (1GbE, bonded 1GbE pair, or 10GbE) should match your
                 desired concurrent throughput needs for reads and
                 writes.</para>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/doc/user-guide-admin/section_cli_keystone_set_quotas.xml b/doc/user-guide-admin/section_cli_keystone_set_quotas.xml
index c03629f052..db16c5b4c8 100644
--- a/doc/user-guide-admin/section_cli_keystone_set_quotas.xml
+++ b/doc/user-guide-admin/section_cli_keystone_set_quotas.xml
@@ -22,7 +22,7 @@
     the OpenStack Compute Service, the OpenStack Block Storage Service,
     and the OpenStack Networking Service.</para>
   <para>Typically, default values are changed because a tenant
-    requires more than 10 volumes, or more than 1TB on a compute node.</para>
+    requires more than 10 volumes, or more than 1 TB on a compute node.</para>
   <note>
     <para>To view all tenants (projects), run:
       <screen><prompt>$</prompt> <userinput>keystone tenant-list</userinput>