diff --git a/doc/admin-guide-cloud/networking/section_networking_arch.xml b/doc/admin-guide-cloud/networking/section_networking_arch.xml index 5a0167f02c..5b5726ff33 100644 --- a/doc/admin-guide-cloud/networking/section_networking_arch.xml +++ b/doc/admin-guide-cloud/networking/section_networking_arch.xml @@ -40,7 +40,7 @@ agent (neutron-*-agent) Runs on each hypervisor to perform local - vSwitch configuration. The agent that runs depends + vSwitch configuration. The agent that runs, depends on the plug-in that you use. Certain plug-ins do not require an agent. @@ -79,12 +79,12 @@ Compute (Nova) interacts with Networking - through calls to its standard API.  As part of + through calls to its standard API. As part of creating a VM, the nova-compute service communicates with the Networking API to plug each virtual NIC on the VM into a particular - network.  + network. The Dashboard (Horizon) integrates with the @@ -106,7 +106,7 @@ >OpenStack Configuration Reference. A standard architectural design includes a cloud controller host, a network gateway host, and a number of hypervisors - for hosting virtual machines. The cloud controller and + for hosting virtual machines. The cloud controller and network gateway can be on the same host. However, if you expect VMs to send significant traffic to or from the Internet, a dedicated network gateway host helps @@ -168,13 +168,13 @@ API network Exposes all OpenStack APIs, including - the Networking API, to tenants. IP + the Networking API, to tenants. IP addresses on this network should be reachable by anyone on the - Internet. The API network might be the + Internet. The API network might be the same as the external network, because it is possible to create an - external-network subnet that is + external-network subnet that has allocated IP ranges that use less than the full range of IP addresses in an IP block.