openstack/devstack
Code Issues Proposed changes

Fix four typos on devstack documentation

Browse Source 
behaviour => behavior
mechansim => mechanism
glustfs => glusterfs
pluggin => plugin

Change-Id: I3de6740e5d4b2b55009614007767458124036b75
Closes-Bug: #1478538
This commit is contained in:
Atsushi SAKAI 2015-07-27 20:42:44 +09:00
parent a3210822ce
commit 2040143409
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
HACKING.rst
View File

@ -355,7 +355,7 @@ your change
* **Should this be upstream** -- DevStack generally does not override * **Should this be upstream** -- DevStack generally does not override
default choices provided by projects and attempts to not default choices provided by projects and attempts to not
unexpectedly modify behaviour. unexpectedly modify behavior.
* **Context in commit messages** -- DevStack touches many different * **Context in commit messages** -- DevStack touches many different
areas and reviewers need context around changes to make good areas and reviewers need context around changes to make good

6
doc/source/plugins.rst
View File

@ -15,7 +15,7 @@ evolves.
Plugin Interface Plugin Interface
================ ================
DevStack supports a standard mechansim for including plugins from DevStack supports a standard mechanism for including plugins from
external repositories. The plugin interface assumes the following: external repositories. The plugin interface assumes the following:
An external git repository that includes a ``devstack/`` top level An external git repository that includes a ``devstack/`` top level
@ -49,7 +49,7 @@ They are added in the following format::
[[local|localrc]] [[local|localrc]]
enable_plugin <NAME> <GITURL> [GITREF] enable_plugin <NAME> <GITURL> [GITREF]
- ``name`` - an arbitrary name. (ex: glustfs, docker, zaqar, congress) - ``name`` - an arbitrary name. (ex: glusterfs, docker, zaqar, congress)
- ``giturl`` - a valid git url that can be cloned - ``giturl`` - a valid git url that can be cloned
- ``gitref`` - an optional git ref (branch / ref / tag) that will be - ``gitref`` - an optional git ref (branch / ref / tag) that will be
cloned. Defaults to master. cloned. Defaults to master.
@ -209,7 +209,7 @@ enough to be an issue).
Ideally a plugin will be included within the ``devstack`` directory of Ideally a plugin will be included within the ``devstack`` directory of
the project they are being tested. For example, the stackforge/ec2-api the project they are being tested. For example, the stackforge/ec2-api
project has its pluggin support in its own tree. project has its plugin support in its own tree.
However, some times a DevStack plugin might be used solely to However, some times a DevStack plugin might be used solely to
configure a backend service that will be used by the rest of configure a backend service that will be used by the rest of