Fix Typos found with misspell

git ls-files | grep -v locale | misspellings -f -

Change-Id: I0dc56ba64ae4bdc681ccf4a1d2d23238f541650d

docs/source/configuration.html

@@ -146,7 +146,7 @@ SERVICE_TOKEN=a682f596-76f3-11e3-b3b2-e716f9080d50
 
             <dt>One syslog to bind them all</dt>
             <dd><em>Default: <code>SYSLOG=False SYSLOG_HOST=$HOST_IP SYSLOG_PORT=516</code></em><br />
-            Logging all services to a single syslog can be convenient.  Enable syslogging by seting <code>SYSLOG</code> to <code>True</code>. If the destination log host is not localhost <code>SYSLOG_HOST</code> and <code>SYSLOG_PORT</code> can be used to direct the message stream to the log host.
+            Logging all services to a single syslog can be convenient.  Enable syslogging by setting <code>SYSLOG</code> to <code>True</code>. If the destination log host is not localhost <code>SYSLOG_HOST</code> and <code>SYSLOG_PORT</code> can be used to direct the message stream to the log host.
             <pre>SYSLOG=True
 SYSLOG_HOST=$HOST_IP
 SYSLOG_PORT=516</pre></dd>

docs/source/guides/multinode-lab.html

@@ -114,11 +114,11 @@ GATEWAY=192.168.42.1
         <p>OpenStack runs as a non-root user that has sudo access to root.  There is nothing special
         about the name, we'll use <code>stack</code> here. Every node must use the same name and
         preferably uid. If you created a user during the OS install you can use it and give it
-        sudo priviledges below.  Otherwise create the stack user:</p>
+        sudo privileges below.  Otherwise create the stack user:</p>
         <pre>groupadd stack
 useradd -g stack -s /bin/bash -d /opt/stack -m stack</pre>
         <p>This user will be making many changes to your system during installation and operation
-        so it needs to have sudo priviledges to root without a password:</p>
+        so it needs to have sudo privileges to root without a password:</p>
         <pre>echo "stack ALL=(ALL) NOPASSWD: ALL" &gt;&gt; /etc/sudoers</pre>
         <p>From here on use the <code>stack</code> user.  <b>Logout</b> and <b>login</b> as the 
         <code>stack</code> user.</p>
@@ -221,7 +221,7 @@ sudo virsh list | grep inst | awk '{print $1}' | xargs -n1 virsh destroy</pre>
         </div>
 
         <h3>Additional Users</h3>
-        <p>DevStack creates two OpenStack users (<code>admin</code> and <code>demo</code>) and two tenants (also <code>admin</code> and <code>demo</code>).  <code>admin</code> is exactly what it sounds like, a priveleged administrative account that is a member of both the <code>admin</code> and <code>demo</code> tenants.  <code>demo</code> is a normal user account that is only a member of the <code>demo</code> tenant.  Creating additional OpenStack users can be done through the dashboard, sometimes it is easier to do them in bulk from a script, especially since they get blown away every time
+        <p>DevStack creates two OpenStack users (<code>admin</code> and <code>demo</code>) and two tenants (also <code>admin</code> and <code>demo</code>).  <code>admin</code> is exactly what it sounds like, a privileged administrative account that is a member of both the <code>admin</code> and <code>demo</code> tenants.  <code>demo</code> is a normal user account that is only a member of the <code>demo</code> tenant.  Creating additional OpenStack users can be done through the dashboard, sometimes it is easier to do them in bulk from a script, especially since they get blown away every time
         <code>stack.sh</code> runs.  The following steps are ripe for scripting:</p>
         <pre># Get admin creds
 . openrc admin admin
@@ -275,7 +275,7 @@ keystone user-role-add --user-id=&lt;bob-user-id&gt; --tenant-id=&lt;bob-tenant-
 vgcreate stack-volumes /dev/sdc</pre>
 
         <h3>Syslog</h3>
-        <p>DevStack is capable of using <code>rsyslog</code> to agregate logging across the cluster.
+        <p>DevStack is capable of using <code>rsyslog</code> to aggregate logging across the cluster.
         It is off by default; to turn it on set <code>SYSLOG=True</code> in <code>local.conf</code>.
         <code>SYSLOG_HOST</code> defaults to <code>HOST_IP</code>; on the compute nodes it 
         must be set to the IP of the cluster controller to send syslog output there.  In the example

docs/source/guides/single-machine.html

@@ -69,9 +69,9 @@
         </div>
 
         <h3>Add your user</h3>
-        <p>We need to add a user to install DevStack.  (if you created a user during install you can skip this step and just give the user sudo priviledges below)</p>
+        <p>We need to add a user to install DevStack.  (if you created a user during install you can skip this step and just give the user sudo privileges below)</p>
         <pre>adduser stack</pre>
-        <p>Since this user will be making many changes to your system, it will need to have sudo priviledges:</p>
+        <p>Since this user will be making many changes to your system, it will need to have sudo privileges:</p>
         <pre>apt-get install sudo -y || yum install -y sudo
 echo "stack ALL=(ALL) NOPASSWD: ALL" &gt;&gt; /etc/sudoers</pre>
         <p>From here on you should use the user you created.  <b>Logout</b> and <b>login</b> as that user.</p>
@@ -113,7 +113,7 @@ SERVICE_PASSWORD=iheartksl</pre>
         <h3>Using OpenStack</h3>
         <p>At this point you should be able to access the dashboard from other computers on the 
         local network.  In this example that would be http://192.168.1.201/ for the dashboard (aka Horizon).
-        Launch VMs and if you give them floating IPs and security group access those VMs will be accessable from other machines on your network.</p>
+        Launch VMs and if you give them floating IPs and security group access those VMs will be accessible from other machines on your network.</p>
 
         <p>Some examples of using the OpenStack command-line clients <code>nova</code> and <code>glance</code>
         are in the shakedown scripts in <code>devstack/exercises</code>.  <code>exercise.sh</code>

docs/source/openrc.html

@@ -60,7 +60,7 @@
           <dd>The introduction of Keystone to the OpenStack ecosystem has standardized the
             term <em>tenant</em> as the entity that owns resources.  In some places references
             still exist to the original Nova term <em>project</em> for this use.  Also,
-            <em>tenant_name</em> is prefered to <em>tenant_id</em>.
+            <em>tenant_name</em> is preferred to <em>tenant_id</em>.
             <pre>OS_TENANT_NAME=demo</pre></dd>
 
           <dt>OS_USERNAME</dt>

tools/build_docs.sh

@@ -17,7 +17,7 @@
 ##                  prevent stray files in the workspace being added tot he docs)
 ## -o <out-dir>     Write the static HTML output to <out-dir>
 ##                  (Note that <out-dir> will be deleted and re-created to ensure it is clean)
-## -g               Update the old gh-pages repo  (set PUSH=1 to actualy push up to RCB)
+## -g               Update the old gh-pages repo  (set PUSH=1 to actually push up to RCB)
 
 # Defaults
 # --------

tools/xen/install_os_domU.sh

@@ -394,7 +394,7 @@ if [ "$WAIT_TILL_LAUNCH" = "1" ]  && [ -e ~/.ssh/id_rsa.pub  ] && [ "$COPYENV" =
 
     # Watch devstack's output (which doesn't start until stack.sh is running,
     # but wait for run.sh (which starts stack.sh) to exit as that is what
-    # hopefully writes the succeded cookie.
+    # hopefully writes the succeeded cookie.
     pid=`ssh_no_check -q stack@$OS_VM_MANAGEMENT_ADDRESS pgrep run.sh`
     ssh_no_check -q stack@$OS_VM_MANAGEMENT_ADDRESS "tail --pid $pid -n +1 -f /tmp/devstack/log/stack.log"