Fixed typos in api-ref and releasenotes directory

This patchset fixes the typo errors in api-ref and
releasenotes directories.
TrivialFix

Change-Id: Ib72e5c4ac7539c1b08adc858b9b3a0071cb3c866
This commit is contained in:
Alex Szarka 2016-07-12 14:14:38 +02:00
parent d3c1ce2635
commit 2a1aad9de7
6 changed files with 26 additions and 16 deletions

View File

@ -106,7 +106,7 @@ Updates an extra spec, by key, for a flavor, by ID.
Normal response codes: 200 Normal response codes: 200
Error response codes: badRequest(400), uauthorized(401), forbidden(403) Error response codes: badRequest(400), unauthorized(401), forbidden(403)
itemNotFound(404), conflict(409) itemNotFound(404), conflict(409)
Request Request

View File

@ -17,7 +17,9 @@ List Hypervisors
Lists hypervisors. Lists hypervisors.
Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the ``policy.json`` file. Policy defaults enable only users with the administrative role to perform
this operation. Cloud providers can change these permissions through
the ``policy.json`` file.
Normal response codes: 200 Normal response codes: 200
@ -54,7 +56,9 @@ List Hypervisors Details
Lists hypervisors details. Lists hypervisors details.
Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the ``policy.json`` file. Policy defaults enable only users with the administrative role to perform
this operation. Cloud providers can change these permissions through
the ``policy.json`` file.
Normal response codes: 200 Normal response codes: 200
@ -114,7 +118,9 @@ Show Hypervisor Statistics
Shows summary statistics for all hypervisors over all compute nodes. Shows summary statistics for all hypervisors over all compute nodes.
Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the ``policy.json`` file. Policy defaults enable only users with the administrative role to perform
this operation. Cloud providers can change these permissions through
the ``policy.json`` file.
Normal response codes: 200 Normal response codes: 200
@ -151,8 +157,9 @@ Show Hypervisor Details
Shows details for a hypervisor. Shows details for a hypervisor.
Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions thro Policy defaults enable only users with the administrative role to perform
ugh the ``policy.json`` file. this operation. Cloud providers can change these permissions through
the ``policy.json`` file.
Normal response codes: 200 Normal response codes: 200
@ -211,8 +218,9 @@ Show Hypervisor Uptime
Shows the uptime for a hypervisor. Shows the uptime for a hypervisor.
Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions thro Policy defaults enable only users with the administrative role to perform
ugh the ``policy.json`` file. this operation. Cloud providers can change these permissions through
the ``policy.json`` file.
Normal response codes: 200 Normal response codes: 200
@ -249,8 +257,9 @@ Search Hypervisor
Search hypervisor by given hypervisor id. Search hypervisor by given hypervisor id.
Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions thro Policy defaults enable only users with the administrative role to perform
ugh the ``policy.json`` file. this operation. Cloud providers can change these permissions through
the ``policy.json`` file.
Normal response code: 200 Normal response code: 200
@ -286,8 +295,9 @@ List Hypervisor Servers
List all servers belong to given hypervisor. List all servers belong to given hypervisor.
Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions thro Policy defaults enable only users with the administrative role to perform
ugh the ``policy.json`` file. this operation. Cloud providers can change these permissions through
the ``policy.json`` file.
Normal response code: 200 Normal response code: 200

View File

@ -3067,7 +3067,7 @@ period_beginning:
type: string type: string
period_ending: period_ending:
description: | description: |
The ending time of the instance usgae audit period. The ending time of the instance usage audit period.
For example, ``2016-06-01 00:00:00``. For example, ``2016-06-01 00:00:00``.
in: body in: body
required: true required: true

View File

@ -488,7 +488,7 @@ The server usage information appears in the ``OS-SRV-USG:launched_at`` and ``OS-
To hide ``addresses`` information for instances in a certain state, set the ``osapi_hide_server_address_states`` configuration option. Set this option to a valid VM state in the ``nova.conf`` configuration file. To hide ``addresses`` information for instances in a certain state, set the ``osapi_hide_server_address_states`` configuration option. Set this option to a valid VM state in the ``nova.conf`` configuration file.
HostId is unique peraccount and is not globally unique. HostId is unique per account and is not globally unique.
Preconditions Preconditions

View File

@ -4,5 +4,5 @@ features:
performed asynchronously. ``instance-actions`` should be used for getting performed asynchronously. ``instance-actions`` should be used for getting
information about the checks results. New approach allows to reduce rpc information about the checks results. New approach allows to reduce rpc
timeouts amount, as previous workflow was fully blocking and checks before timeouts amount, as previous workflow was fully blocking and checks before
live-migration make blocking rpc request to both source and destionation live-migration make blocking rpc request to both source and destination
compute node. compute node.

View File

@ -1,7 +1,7 @@
--- ---
features: features:
- | - |
The 2.32 microverison adds support for virtual device The 2.32 microversion adds support for virtual device
role tagging. Device role tagging is an answer to the role tagging. Device role tagging is an answer to the
question 'Which device is which, inside the guest?' When question 'Which device is which, inside the guest?' When
booting an instance, an optional arbitrary 'tag' booting an instance, an optional arbitrary 'tag'