Merge "Fix some typos in cinder doc"

This commit is contained in:
Zuul 2017-12-19 16:27:43 +00:00 committed by Gerrit Code Review
commit 8b389b8b21
6 changed files with 6 additions and 6 deletions

View File

@ -126,7 +126,7 @@ To create a volume type that enables replication using Live Volume:
If QOS options are enabled on the Storage Center they can be enabled via extra
specs. The name of the Volume QOS can be specified via the
``storagetype:volumeqos`` extra spec. Likewise the name of the Group QOS to
use can be specificed via the ``storagetype:groupqos`` extra spec. Volumes
use can be specified via the ``storagetype:groupqos`` extra spec. Volumes
created with these extra specs set will be added to the specified QOS groups.
To create a volume type that sets both Volume and Group QOS:

View File

@ -523,7 +523,7 @@ Interval and Retries
By default, ``interval`` and ``retries`` are ``3`` seconds and ``200`` retries
respectively. These determine how long (``interval``) and how many times
(``retries``) a user is willing to wait for a single Rest call,
``3*200=600seconds``. Depending on usage, these may need to be overriden by
``3*200=600seconds``. Depending on usage, these may need to be overridden by
the user in the cinder.conf. For example, if performance is a factor, then the
``interval`` should be decreased to check the job status more frequently, and
if multiple concurrent provisioning requests are issued then ``retries``

View File

@ -102,7 +102,7 @@ should be bind mounted into the Linux containers.
Note that the user IDs present in the containers should match as that in the
host machines. For example, the containers running cinder and glance
services should be priviledged containers.
services should be privileged containers.
To use Spectrum Scale driver in this deployment mode, set the ``volume_driver``
in the ``cinder.conf`` as:

View File

@ -6,7 +6,7 @@ Introduction:
-------------
This directory is intended to hold any documentation that relates to
how to contirbute to Cinder or how the project is managed. Some of this
how to contribute to Cinder or how the project is managed. Some of this
content was previous under 'developer' in openstack-manuals. The content
of the documentation, however, goes beyond just developers to anyone
contributing to the project, thus the change in naming.

View File

@ -78,7 +78,7 @@ During the documentation build a number of things happen:
will look consistent with all the other OpenStack documentation.
* The resulting HTML is put into ``doc/build/html``.
* Sample files like cinder.conf.sample are generated and put into ``doc/soure/_static``.
* Sample files like cinder.conf.sample are generated and put into ``doc/source/_static``.
* All of Cinder's ``.py`` files are processed and the docstrings are used to
generate the files under ``doc/source/contributor/api``

View File

@ -251,7 +251,7 @@ normal replication operation. So they can be assigned in the model update and
later on used by the driver, for example during the failover.
To avoid using magic strings drivers must use values defined by the
``ReplicationsSatus`` class in ``cinder/objects/fields.py`` file and
``ReplicationStatus`` class in ``cinder/objects/fields.py`` file and
these are:
- ``ERROR``: When setting the replication failed on creation, retype, or