diff --git a/doc/admin-guide-cloud/source/networking_adv-features.rst b/doc/admin-guide-cloud/source/networking_adv-features.rst index 84eff45731..528cc7b7e1 100644 --- a/doc/admin-guide-cloud/source/networking_adv-features.rst +++ b/doc/admin-guide-cloud/source/networking_adv-features.rst @@ -46,7 +46,7 @@ configuration of plug-ins supporting the provider extension: +----------------------+-----------------------------------------------------+ | Term | Description | +======================+=====================================================+ -| **virtual network** |An Networking L2 network (identified by a UUID and | +| **virtual network** |A Networking L2 network (identified by a UUID and | | |optional name) whose ports can be attached as vNICs | | |to Compute instances and to various Networking | | |agents. The Open vSwitch and Linux Bridge plug-ins | diff --git a/doc/admin-guide-cloud/source/networking_config-identity.rst b/doc/admin-guide-cloud/source/networking_config-identity.rst index d2aef2ec6a..cf642a003a 100644 --- a/doc/admin-guide-cloud/source/networking_config-identity.rst +++ b/doc/admin-guide-cloud/source/networking_config-identity.rst @@ -38,7 +38,7 @@ Configure Identity service for Networking The way that you create a Networking endpoint entry depends on whether you are using the SQL or the template catalog driver: - - If you use the *SQL driver*, run the following command with the + - If you are using the *SQL driver*, run the following command with the specified region (``$REGION``), IP address of the Networking server (``$IP``), and service ID (``$NEUTRON_SERVICE_ID``, obtained in the previous step). diff --git a/doc/admin-guide-cloud/source/networking_introduction.rst b/doc/admin-guide-cloud/source/networking_introduction.rst index e406be5d76..35b53138cb 100644 --- a/doc/admin-guide-cloud/source/networking_introduction.rst +++ b/doc/admin-guide-cloud/source/networking_introduction.rst @@ -271,7 +271,7 @@ create a firewall that applies the policy. **Allowed-address-pairs.** -``Allowed-address-pairs`` enable you to specify +``Allowed-address-pairs`` enables you to specify mac_address/ip_address(cidr) pairs that pass through a port regardless of subnet. This enables the use of protocols such as VRRP, which floats an IP address between two instances to enable fast data plane failover. @@ -283,7 +283,7 @@ an IP address between two instances to enable fast data plane failover. **Basic allowed-address-pairs operations.** -- Create a port with a specified allowed address pairs: +- Create a port with a specified allowed address pair: .. code:: console diff --git a/doc/admin-guide-cloud/source/networking_use.rst b/doc/admin-guide-cloud/source/networking_use.rst index 4b1eec5002..2f886453e6 100644 --- a/doc/admin-guide-cloud/source/networking_use.rst +++ b/doc/admin-guide-cloud/source/networking_use.rst @@ -146,7 +146,7 @@ advanced network operations: | | ``$ neutron subnet-create`` | | | ``net1 10.0.0.0/24 --enable-dhcp False`` | +-------------------------------+--------------------------------------------+ -|Specified set of host routes. | | +|Specifies a set of host routes | | | | | | | ``$ neutron subnet-create`` | | | ``test-net1 40.0.0.0/24 --host-routes``| @@ -200,7 +200,7 @@ complete basic VM networking operations: | |``$ neutron port-list --device_id VM_ID``| +----------------------------------+-----------------------------------------+ |Searches for ports, but shows | | -|onlythe ``mac_address`` of | | +|only the ``mac_address`` of | | |the port. | | | | | | | ``$ neutron port-list --field`` | @@ -271,7 +271,7 @@ complete advanced VM creation operations: Cloud images that distribution vendors offer usually have only one active NIC configured. When you boot with multiple NICs, you must - configure additional interfaces on the image or the NICS are not + configure additional interfaces on the image or the NICs are not reachable. The following Debian/Ubuntu-based example shows how to set up the