diff --git a/doc/arch-design/network_focus/section_architecture_network_focus.xml b/doc/arch-design/network_focus/section_architecture_network_focus.xml
index 98e80a7ef9..fac292f2d4 100644
--- a/doc/arch-design/network_focus/section_architecture_network_focus.xml
+++ b/doc/arch-design/network_focus/section_architecture_network_focus.xml
@@ -7,12 +7,12 @@
     <title>Architecture</title>
     <para>Network focused OpenStack architectures have many
         similarities to other OpenStack architecture use cases. There
-        a number of very specific considerations to keep in mind when
+        are a number of very specific considerations to keep in mind when
         designing for a network-centric or network-heavy application
         environment.</para>
-    <para>Networks exist to serve a as medium of transporting data
+    <para>Networks exist to serve as a medium of transporting data
         between systems. It is inevitable that an OpenStack design
-        have inter-dependencies with non-network portions of OpenStack
+        has inter-dependencies with non-network portions of OpenStack
         as well as on external systems. Depending on the specific
         workload, there may be major interactions with storage systems
         both within and external to the OpenStack environment. For
@@ -152,7 +152,7 @@
         protocols. While OpenStack was initially built with only IPv4
         support, Networking now supports IPv6 and dual-stacked networks.
         Note that, as of the Icehouse release, this only includes
-        stateless address autoconfiguration but work is in
+        stateless address auto configuration but work is in
         progress to support stateless and stateful DHCPv6 as well as
         IPv6 floating IPs without NAT. Some workloads become possible
         through the use of IPv6 and IPv6 to IPv4 reverse transition