diff --git a/doc/admin-guide-cloud-rst/source/blockstorage-driver-filter-weighing.rst b/doc/admin-guide-cloud-rst/source/blockstorage-driver-filter-weighing.rst index 07ab2af58a..e3de643079 100644 --- a/doc/admin-guide-cloud-rst/source/blockstorage-driver-filter-weighing.rst +++ b/doc/admin-guide-cloud-rst/source/blockstorage-driver-filter-weighing.rst @@ -22,7 +22,7 @@ property to determine the best back end, but that is not always perfect. If a back end has the ability to provide a more accurate back-end specific value you can use that as part of the weighing. Another example of when the driver filter and weigher can prove useful is if a back end -exists where there is a hard limit of 1000 volumes. The maxmimum volume +exists where there is a hard limit of 1000 volumes. The maximum volume size is 500 GB. Once 75% of the total space is occupied the performance of the back end degrades. The driver filter and weigher can provide a way for these limits to be checked for. @@ -338,7 +338,7 @@ properties:: goodness_function = "55" The above is an example of how back-end specific properties can be used -in the fitler and goodness functions. In this example the LVM driver's +in the filter and goodness functions. In this example the LVM driver's ``total\_volumes`` capability is being used to determine which host gets used during a volume request. In the above example, lvm-1 and lvm-2 will handle volume requests for all volumes with a size less than 5 GB. The diff --git a/doc/admin-guide-cloud-rst/source/networking_config-plugins.rst b/doc/admin-guide-cloud-rst/source/networking_config-plugins.rst index fc1aff9e62..aac4d1ddeb 100644 --- a/doc/admin-guide-cloud-rst/source/networking_config-plugins.rst +++ b/doc/admin-guide-cloud-rst/source/networking_config-plugins.rst @@ -154,7 +154,7 @@ formerly known as Nicira NVP. when a tenant creates a network. You can get this value from the Transport Zones page for the NSX-mh manager: - Alternatively the transport zone identfier can be retrieved by query + Alternatively the transport zone identifier can be retrieved by query the NSX-mh API: ``/ws.v1/transport-zone`` .. code:: ini diff --git a/doc/admin-guide-cloud-rst/source/objectstorage_components.rst b/doc/admin-guide-cloud-rst/source/objectstorage_components.rst index 115e0da668..b82c0b55af 100644 --- a/doc/admin-guide-cloud-rst/source/objectstorage_components.rst +++ b/doc/admin-guide-cloud-rst/source/objectstorage_components.rst @@ -130,7 +130,7 @@ outages of storage servers without losing all replicas of the data. As mentioned earlier, everything in Object Storage is stored, by default, three times. Swift will place each replica "as-uniquely-as-possible" to ensure both high availability and high -durability. This means that when chosing a replica location, Object +durability. This means that when choosing a replica location, Object Storage chooses a server in an unused zone before an unused server in a zone that already has a replica of the data. diff --git a/doc/admin-guide-cloud/blockstorage/section_driver_filter_weighing.xml b/doc/admin-guide-cloud/blockstorage/section_driver_filter_weighing.xml index 00a986bf5b..51e55bd549 100644 --- a/doc/admin-guide-cloud/blockstorage/section_driver_filter_weighing.xml +++ b/doc/admin-guide-cloud/blockstorage/section_driver_filter_weighing.xml @@ -41,7 +41,7 @@ Another example of when the driver filter and weigher can prove useful is if a back end exists where there is a hard - limit of 1000 volumes. The maxmimum volume size is + limit of 1000 volumes. The maximum volume size is 500 GB. Once 75% of the total space is occupied the performance of the back end degrades. The driver filter and weigher can provide a way for these limits to be checked @@ -498,7 +498,7 @@ goodness_function = "55" The above is an example of how back-end specific properties - can be used in the fitler and goodness functions. In this + can be used in the filter and goodness functions. In this example the LVM driver's 'total_volumes' capability is being used to determine which host gets used during a volume request. diff --git a/doc/admin-guide-cloud/networking/section_networking_adv_features.xml b/doc/admin-guide-cloud/networking/section_networking_adv_features.xml index e0c2a649fb..5765fe7b54 100644 --- a/doc/admin-guide-cloud/networking/section_networking_adv_features.xml +++ b/doc/admin-guide-cloud/networking/section_networking_adv_features.xml @@ -392,7 +392,7 @@ When a port is created in Networking it is associated with a security group. If a security group is not specified the port is associated with a 'default' security group. By default, this group drops all ingress traffic and allows all egress. Rules can be - added to this group in order to change the behaviour. + added to this group in order to change the behavior. To use the Compute security group APIs or use Compute to orchestrate the creation of ports for instances on specific security groups, you must complete additional configuration. You must configure the /etc/nova/nova.conf file and diff --git a/doc/admin-guide-cloud/networking/section_networking_config-plugins.xml b/doc/admin-guide-cloud/networking/section_networking_config-plugins.xml index d347216241..4551880983 100644 --- a/doc/admin-guide-cloud/networking/section_networking_config-plugins.xml +++ b/doc/admin-guide-cloud/networking/section_networking_config-plugins.xml @@ -129,7 +129,7 @@ nsx_controllers = API_ENDPOINT_LIST # comma-separated The UUID of the NSX-mh transport zone that should be used by default when a tenant creates a network. You can get this value from the Transport Zones page for the NSX-mh manager: - Alternatively the transport zone identfier can be retrieved by query the NSX-mh + Alternatively the transport zone identifier can be retrieved by query the NSX-mh API: /ws.v1/transport-zone default_tz_uuid = TRANSPORT_ZONE_UUID diff --git a/doc/common/section_objectstorage-components.xml b/doc/common/section_objectstorage-components.xml index bf239a0400..5e2fd4eb77 100644 --- a/doc/common/section_objectstorage-components.xml +++ b/doc/common/section_objectstorage-components.xml @@ -119,7 +119,7 @@ losing all replicas of the data. As mentioned earlier, everything in Object Storage is stored, by default, three times. Swift will place each replica "as-uniquely-as-possible" to ensure both high - availability and high durability. This means that when chosing a replica location, + availability and high durability. This means that when choosing a replica location, Object Storage chooses a server in an unused zone before an unused server in a zone that already has a replica of the data.
diff --git a/doc/networking-guide/source/intro_os_networking_overview.rst b/doc/networking-guide/source/intro_os_networking_overview.rst index 25f4c548d0..e38bed6724 100644 --- a/doc/networking-guide/source/intro_os_networking_overview.rst +++ b/doc/networking-guide/source/intro_os_networking_overview.rst @@ -143,7 +143,7 @@ security group rules. When a port is created in Networking it is associated with a security group. If a security group is not specified the port is associated with a 'default' security group. By default, this group drops all ingress traffic and allows all egress. Rules can be added to this group in -order to change the behaviour. +order to change the behavior. Extensions ----------