Fix four typos on devstack documentation
behaviour => behavior
mechansim => mechanism
glustfs => glusterfs
pluggin => plugin
Change-Id: I3de6740e5d4b2b55009614007767458124036b75
Closes-Bug: #1478538
diff --git a/doc/source/plugins.rst b/doc/source/plugins.rst
index 1b6f5e3..803dd08 100644
--- a/doc/source/plugins.rst
+++ b/doc/source/plugins.rst
@@ -15,7 +15,7 @@
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:
An external git repository that includes a ``devstack/`` top level
@@ -49,7 +49,7 @@
[[local|localrc]]
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
- ``gitref`` - an optional git ref (branch / ref / tag) that will be
cloned. Defaults to master.
@@ -209,7 +209,7 @@
Ideally a plugin will be included within the ``devstack`` directory of
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
configure a backend service that will be used by the rest of