aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/developer-env.md2
-rw-r--r--docs/integration-guide.md6
2 files changed, 4 insertions, 4 deletions
diff --git a/docs/developer-env.md b/docs/developer-env.md
index ab2ee33a6..fe1916bb6 100644
--- a/docs/developer-env.md
+++ b/docs/developer-env.md
@@ -1,6 +1,6 @@
# Developer env
-The basic starting enviroment will be created using `docker-compose`.
+The basic starting environment will be created using `docker-compose`.
This environment will start up the openstack services listed in the
compose directory.
diff --git a/docs/integration-guide.md b/docs/integration-guide.md
index 54bfc26fe..1e18887f3 100644
--- a/docs/integration-guide.md
+++ b/docs/integration-guide.md
@@ -6,13 +6,13 @@ via docker-compose using docker-compose YML files. Each container set has a
common YML and associated openstack.env. The openstack.env file describes the
command line environment to pass to the docker-compose yml files.
-## Why integate with Kolla?
+## Why integrate with Kolla?
Integrating with Kolla takes a hard part of managing an OpenStack system,
specifically managing the container images, and places the burden on a third
party project. We strive to do an excellent job of providing world-class
OpenStack containers at least as a reference architecture, and possibly as what
-may be desireable to deploy into live production.
+may be desirable to deploy into live production.
## Docker Command Line Arguments
@@ -37,7 +37,7 @@ executed via docker-compose.
Rather then document which individual containers require specific configuration
variables, Kolla integration requires passing all configuration variables to
all containers. This allows a simple method of ensuring every type of node
-(controller, storage, compute) recieves the same configuration.
+(controller, storage, compute) receives the same configuration.
### Environment Variable KEY/VALUE pairs