aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStanislav Chlebec <stanislav.chlebec@pantheon.tech>2018-11-05 10:38:17 +0100
committerStanislav Chlebec <stanislav.chlebec@pantheon.tech>2018-11-05 10:39:32 +0100
commit1359ae6401357c9381c0f0e0cf997a48fb8272d2 (patch)
tree7d9006750e69204ce4668c31526d0dadefafbcb0
parent5dd0bab482f4740dec66f5a1a1e1dc8b4fef2296 (diff)
Fix typos
Change-Id: Ie185b7d522d6975bd008ca8276d4857f0c94904b Signed-off-by: Stanislav Chlebec <stanislav.chlebec@pantheon.tech> Issue-ID: AAF-582
-rw-r--r--docs/source/features/configure_execution.rst4
-rw-r--r--docs/source/features/consuming_scripts.rst8
-rw-r--r--docs/source/features/openstack.rst2
-rw-r--r--docs/source/install/known_issues.rst2
4 files changed, 8 insertions, 8 deletions
diff --git a/docs/source/features/configure_execution.rst b/docs/source/features/configure_execution.rst
index df08605..e42c04d 100644
--- a/docs/source/features/configure_execution.rst
+++ b/docs/source/features/configure_execution.rst
@@ -11,7 +11,7 @@ Settings configuration file
The first mechanism refers to the process to replace default configuration
values in the settings configuration file. This file needs to be placed into
the *./etc* folder and named *settings.yaml*. It must contain the key/pair
-configuration values that will be overriden.
+configuration values that will be overridden.
.. note::
@@ -55,7 +55,7 @@ Parameters
----------
The **skip_get_images** and **skip_install** are the only two configuration
-values that can be overriden using *-g* and *-i* respectively by the run scripts
+values that can be overridden using *-g* and *-i* respectively by the run scripts
(*./tools/run.sh* and *.\\tools\\Run.ps1*).
.. note::
diff --git a/docs/source/features/consuming_scripts.rst b/docs/source/features/consuming_scripts.rst
index 4290c25..20fe2ed 100644
--- a/docs/source/features/consuming_scripts.rst
+++ b/docs/source/features/consuming_scripts.rst
@@ -3,13 +3,13 @@ Using the provisioning scripts
==============================
Vagrant is a platform that uses prebaked images called
-*vagrant boxes* to guarranty that running multiple times a
+*vagrant boxes* to guarantee that running multiple times a
provisioning script will result in an expected output. This
mechanism is crucial for reducing the number of external factors
during the creation, development and testing of provisioning scripts.
-However, it's possible to provide an ONAP development enviroment
+However, it's possible to provide an ONAP development environment
without having to install Vagrant tool. This document explains how to
-consume the provisioning scripts localed in **./lib** folder to
+consume the provisioning scripts located in **./lib** folder to
provision a development environment and the environment variables
that modifies their behavior.
@@ -52,7 +52,7 @@ and Available Inventory (AAI) service will be required to load the
Lastly, every script has defined a initialization function with
*init_* as prefix. This function is the starting point to provision
the chosen ONAP service. This example uses the *init_aai* function
-to provision a AAI Developement environment.
+to provision a AAI Development environment.
.. note::
diff --git a/docs/source/features/openstack.rst b/docs/source/features/openstack.rst
index f44bc62..58bcc97 100644
--- a/docs/source/features/openstack.rst
+++ b/docs/source/features/openstack.rst
@@ -5,7 +5,7 @@ OpenStack Provider
It's possible to use Vagrant to provision VMs on OpenStack using the
`Vagrant OpenStack Cloud Provider <https://github.com/ggiamarchi/vagrant-openstack-provider/>`.
The only requirement for the Cloud provider is to have an Ubuntu Cloud
-image accesible to your tenant and a Security Rule that allows to do
+image accessible to your tenant and a Security Rule that allows to do
SSH into the instance.
Environment variables
diff --git a/docs/source/install/known_issues.rst b/docs/source/install/known_issues.rst
index 8db55e7..6a1bd4a 100644
--- a/docs/source/install/known_issues.rst
+++ b/docs/source/install/known_issues.rst
@@ -9,7 +9,7 @@ If the **vagrant-vbguest** plugin is installed on the host, then an
updated version of the Virtualbox guest additions will be installed
on the guest in the /opt directory. Once this projects Vagrantfile
mounts the ./opt directory on the host to the /opt directory on the
-guest during the provisioning process, the guest addtions on the
+guest during the provisioning process, the guest additions on the
guest are hidden and subsequent mounts of shared directories with the
host will fail.