openstack/tripleo-docs
Code Issues Proposed changes

Fixed typos across the TripleO documentation

Browse Source 
This patch fixes some typos in the current documentation.

Change-Id: I35155244d581ddfc316064e35e851f55b6d853f1
This commit is contained in:
Carlos Camacho 2016-03-31 10:30:51 +02:00
parent a4a0b1588a
commit 3050f3c5c7
6 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/advanced_deployment/extra_config.rst
View File

@ -248,7 +248,7 @@ environment which enables the configuration.
The "actions" property of the `OS::Heat::SoftwareDeployments` resource may be
used to specify when the configuration should be applied, e.g only on CREATE,
only on DELETE etc. If this is ommitted, the heat default is to apply the
only on DELETE etc. If this is omitted, the heat default is to apply the
config on CREATE and UPDATE, e.g on initial deployment and every subsequent
update.

2
doc/source/advanced_deployment/node_config.rst
View File

@ -3,7 +3,7 @@
Modifying default node configuration
====================================
Many service configurarion options are already exposed via parameters in the
Many service configuration options are already exposed via parameters in the
top-level `overcloud.yaml` template, and these options should
be used wherever available to influence overcloud configuration.

4
doc/source/advanced_deployment/tripleo.sh.rst
View File

@ -80,8 +80,8 @@ are made in order to check the stack creation:
- Create a subnet in the nova network.
- Create a test stack called tenant-stack, using heat, which spawns a guest in
the overcloud and attach it to the nova network.
- Create a test stack called tenant-stack, using heat, which spawns a guest
in the overcloud and attach it to the nova network.
- Ping the floating IP address assigned to the new guest.

2
doc/source/contributions/contributions.rst
View File

@ -31,7 +31,7 @@ Learn `how to contribute into TripleO Docs
Reporting Bugs
--------------
**OpenStack Upstream**: If you find bugs or volnurabilities which affect
**OpenStack Upstream**: If you find bugs or vulnerabilities which affect
upstream projects, please follow OpenStack's process of filing bugs.
* Learn `how to create Bugs in OpenStack

2
doc/source/post_deployment/scale_roles.rst
View File

@ -13,7 +13,7 @@ the following command can be used::
.. note::
When scaling down random servers of specified role will be deleted, how to
delete specific nodes is decribed in :ref:`delete_nodes`.
delete specific nodes is described in :ref:`delete_nodes`.
.. note::
The different scale parameters can be seen in the output of::

4
doc/source/troubleshooting/troubleshooting-overcloud.rst
View File

@ -19,7 +19,7 @@ has failed::
| 7e88af95-535c-4a55-b78d-2c3d9850d854 | overcloud | CREATE_FAILED | 2015-04-06T17:57:16Z |
+--------------------------------------+------------+--------------------+----------------------+
Occassionally, Heat is not even able to create the the stack, so the ``heat
Occasionally, Heat is not even able to create the the stack, so the ``heat
stack-list`` output will be empty. If this is the case, observe the message
that was printed to the terminal when ``instack-deploy-overcloud`` or ``heat
stack-create`` was run.
@ -52,7 +52,7 @@ in the resulting table.
For example, **Maintenance** goes to ``True`` automatically, if wrong power
credentials are provided.
* If **Provision State** is ``available`` then the problem occured before
* If **Provision State** is ``available`` then the problem occurred before
bare metal deployment has even started. Proceed with `Debugging Using Heat`_.
* If **Provision State** is ``active`` and **Power State** is ``power on``,