From ea172ef85ffa070b627361bc2e43985fd6e3444c Mon Sep 17 00:00:00 2001 From: zhufl Date: Thu, 9 Jan 2020 15:49:49 +0800 Subject: [PATCH] Fix typos in nova doc This is to fix the following typos: regadless users's possile caculated Change-Id: If47adefa59f01b7f2ebcee5b7e07e0260df113e4 --- api-guide/source/server_concepts.rst | 2 +- doc/source/admin/availability-zones.rst | 2 +- nova/api/openstack/compute/rest_api_version_history.rst | 8 ++++---- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/api-guide/source/server_concepts.rst b/api-guide/source/server_concepts.rst index 1d1a139c6dee..611e1fe2eccc 100644 --- a/api-guide/source/server_concepts.rst +++ b/api-guide/source/server_concepts.rst @@ -85,7 +85,7 @@ server status is one of the following values: - ``VERIFY_RESIZE``: System is awaiting confirmation that the server is operational after a move or resize. -Server status is caculated from vm_state and task_state, which +Server status is calculated from vm_state and task_state, which are exposed to administrators: - vm_state describes a VM's current stable (not transition) state. That is, if diff --git a/doc/source/admin/availability-zones.rst b/doc/source/admin/availability-zones.rst index 5fa0f974d629..224242da0967 100644 --- a/doc/source/admin/availability-zones.rst +++ b/doc/source/admin/availability-zones.rst @@ -252,7 +252,7 @@ associating it with an AZ in the process, and add host to it using the .. note:: While it is possible to add a host to multiple host aggregates, it is not - possile to add them to multiple availability zones. Attempting to add a + possible to add them to multiple availability zones. Attempting to add a host to multiple host aggregates associated with differing availability zones will result in a failure. diff --git a/nova/api/openstack/compute/rest_api_version_history.rst b/nova/api/openstack/compute/rest_api_version_history.rst index c47a4b44d4c7..cbdae2707a03 100644 --- a/nova/api/openstack/compute/rest_api_version_history.rst +++ b/nova/api/openstack/compute/rest_api_version_history.rst @@ -10,7 +10,7 @@ user documentation. --- This is the initial version of the v2.1 API which supports -microversions. The V2.1 API is from the REST API users's point of +microversions. The V2.1 API is from the REST API users' point of view exactly the same as v2.0 except with strong input validation. A user can specify a header in the API request:: @@ -433,19 +433,19 @@ API endpoints as below:: The ``os-security-group-default-rules`` API was completely removed in the 21.0.0 (Ussuri) release. On deployments newer than this, the APIs will - return HTTP 410 (Gone) regadless of the requested microversion. + return HTTP 410 (Gone) regardless of the requested microversion. .. versionchanged:: 21.0.0 The ``os-networks`` API was partially removed in the 21.0.0 (Ussuri) release. On deployments newer than this, some endpoints of the API will - return HTTP 410 (Gone) regadless of the requested microversion. + return HTTP 410 (Gone) regardless of the requested microversion. .. versionchanged:: 21.0.0 The ``os-tenant-networks`` API was partially removed in the 21.0.0 (Ussuri) release. On deployments newer than this, some endpoints of the API will - return HTTP 410 (Gone) regadless of the requested microversion. + return HTTP 410 (Gone) regardless of the requested microversion. 2.37 ----