Fix some spelling typo in manual and program output

Fixed following typos.
 infomation -> information
 initilization -> initialization
 intialize -> initialize
 compatability -> compatibility
 compatability -> compatibility
 quering -> querying
 initilization -> initialization
 infomation -> information
 incomming -> incoming

Also fixed some small typo in source comment.

Change-Id: I381aed76094f19f8ef7e821e965fafb0dfe900b2
Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
This commit is contained in:
Zhao Lei 2015-09-24 21:10:36 +08:00
parent d4f949c0ac
commit 0f140c7b96
7 changed files with 9 additions and 9 deletions

View File

@ -117,7 +117,7 @@ Mistral configuration is needed for getting it work correctly either with real O
connection = postgresql://<user>:<password>@localhost:5432/mistral
8. **If you are not using OpenStack, skip this item.** Update *mistral/actions/openstack/mapping.json* file which contains all allowed OpenStack actions,
according to the specific client versions of OpenStack projects in your deployment. Please find more detailed infomation in *tools/get_action_list.py* script.
according to the specific client versions of OpenStack projects in your deployment. Please find more detailed information in *tools/get_action_list.py* script.
Before the first run
--------------------
@ -132,7 +132,7 @@ For updating the database to the latest revision type::
For more detailed information about *mistral-db-manage* script please see migration readme `here <https://github.com/openstack/mistral/blob/master/mistral/db/sqlalchemy/migration/alembic_migrations/README.md>`__.
| NOTE: For users want a dry run with SQLite database backend(not used in production), *mistral-db-manage* is not recommended for database initialization because of `SQLite limitations <http://www.sqlite.org/omitted.html>`_. Please use sync_db script described below instead for database initilization.
| NOTE: For users want a dry run with SQLite database backend(not used in production), *mistral-db-manage* is not recommended for database initialization because of `SQLite limitations <http://www.sqlite.org/omitted.html>`_. Please use sync_db script described below instead for database initialization.
Before starting Mistral server, run sync_db script. It prepares the DB, creates in it with all standard actions and standard workflows which Mistral provides for all mistral users.

View File

@ -10,7 +10,7 @@ How to write an Action Plugin
class RunnerAction(base.Action):
def __init__(self, param):
# store the incomming params
# store the incoming params
self.param = param
def run(self):

View File

@ -70,7 +70,7 @@ either with real OpenStack environment or without OpenStack environment.
connection = postgresql://<user>:<password>@<database-host>:5432/mistral
8. **If you are not using OpenStack, skip this item.** Update mistral/actions/openstack/mapping.json file which contains all allowed OpenStack actions, according to the specific client versions of OpenStack projects in your deployment. Please find more detailed infomation in tools/get_action_list.py script.
8. **If you are not using OpenStack, skip this item.** Update mistral/actions/openstack/mapping.json file which contains all allowed OpenStack actions, according to the specific client versions of OpenStack projects in your deployment. Please find more detailed information in tools/get_action_list.py script.
9. Configure Task affinity feature if needed. It is needed for distinguishing either single task executor or one task executor from group of task executors::

View File

@ -74,7 +74,7 @@ Before starting Mistral server, run *mistral-db-manage populate* command. It pre
For more detailed information about *mistral-db-manage* script please see :doc:`Mistral Upgrade Guide </guides/upgrade_guide>`.
**NOTE**: For users who want a dry run with **SQLite** database backend(not used in production), *mistral-db-manage* is not recommended for database initialization because of `SQLite limitations <http://www.sqlite.org/omitted.html>`_. Please use sync_db script described below instead for database initilization.
**NOTE**: For users who want a dry run with **SQLite** database backend(not used in production), *mistral-db-manage* is not recommended for database initialization because of `SQLite limitations <http://www.sqlite.org/omitted.html>`_. Please use sync_db script described below instead for database initialization.
**If you use virtualenv**::

View File

@ -179,7 +179,7 @@ class ActionsController(rest.RestController, hooks.HookController):
:param marker: Optional. Pagination marker for large data sets.
:param limit: Optional. Maximum number of resources to return in a
single result. Default value is None for backward
compatability.
compatibility.
:param sort_keys: Optional. Columns to sort results by.
Default: name.
:param sort_dirs: Optional. Directions to sort corresponding to

View File

@ -292,7 +292,7 @@ def get_workflow_definitions(limit=None, marker=None, sort_keys=None,
)
except Exception as e:
raise exc.DBQueryEntryException(
"Failed when quering database, error type: %s, "
"Failed when querying database, error type: %s, "
"error message: %s" % (e.__class__.__name__, e.message)
)
@ -402,7 +402,7 @@ def get_action_definitions(limit=None, marker=None, sort_keys=['name'],
)
except Exception as e:
raise exc.DBQueryEntryException(
"Failed when quering database, error type: %s, "
"Failed when querying database, error type: %s, "
"error message: %s" % (e.__class__.__name__, e.message)
)

View File

@ -123,7 +123,7 @@ class ServiceTest(base.BaseTest):
def setUp(self):
super(ServiceTest, self).setUp()
# Re-intialize the global service coordinator object, in order to use
# Re-initialize the global service coordinator object, in order to use
# new coordination configuration.
coordination.cleanup_service_coordinator()