CI: Add codespell to pep8

Fix existing spelling errors

Change-Id: Ie689cf5a344aaa630a4860448b09242333a8e119

5 files changed, 6 insertions, 6 deletions

diff --git a/specs/internal-tls-endpoints.rst b/specs/internal-tls-endpoints.rst
index f2b23db0b..08721b69a 100644
--- a/specs/internal-tls-endpoints.rst
+++ b/specs/internal-tls-endpoints.rst
@@ -113,7 +113,7 @@ Work Items
      disables certificate verification.
    - Ensure that all tasks that interact with OpenStack APIs support disabling
      certificate verification.
-   - Fix heat-api bootstrap process, which currently requires valid certficate,
+   - Fix heat-api bootstrap process, which currently requires valid certificate,
      probably by moving domain/user creation out of the container, and into the
      ansible itself.
    - Allow for providing a CA used to verify connections to the service backends.
diff --git a/specs/kubernetes-deployment.rst b/specs/kubernetes-deployment.rst
index f96946e34..e451f643c 100644
--- a/specs/kubernetes-deployment.rst
+++ b/specs/kubernetes-deployment.rst
@@ -199,7 +199,7 @@ At the broadest level, OpenStack can split up into two main roles, Controller
 and Compute. With Kubernetes, the role definition layer changes.
 Kolla-kubernetes will still need to define Compute nodes, but not Controller
 nodes. Compute nodes hold the libvirt container and the running vms. That
-service cannont migrate because the vms associated with it exist on the node.
+service cannot migrate because the vms associated with it exist on the node.
 However, the Controller role is more flexible. The Kubernetes layer provides IP
 persistence so that APIs will remain active and abstracted from the operator's
 view [15]. kolla-kubernetes can direct Controller services away from the Compute
@@ -245,7 +245,7 @@ kibana as the default logging mechanism.
 
 The community will implement centralized logging by using a 'side car' container
 in the Kubernetes pod [17]. The logging service will trace the logs from the
-shared volume of the running serivce and send the data to elastic search. This
+shared volume of the running service and send the data to elastic search. This
 solution is ideal because volumes are shared among the containers in a pod.
 
 Implementation
diff --git a/specs/logging-with-heka.rst b/specs/logging-with-heka.rst
index 8087a6a41..c8abc03cb 100644
--- a/specs/logging-with-heka.rst
+++ b/specs/logging-with-heka.rst
@@ -167,7 +167,7 @@ Handling HAProxy and Keepalived
 
 As already mentioned HAProxy and Keepalived do not support logging to files.
 This means that some other mechanism should be used for these two services (and
-any other services that only suppport logging to Syslog).
+any other services that only support logging to Syslog).
 
 Our prototype has demonstrated that we can make Heka act as a Syslog server.
 This works by using Heka's ``UdpInput`` plugin with its ``net`` option set
diff --git a/specs/multiple-globals-files.rst b/specs/multiple-globals-files.rst
index ab9dc8767..1c0ed9314 100644
--- a/specs/multiple-globals-files.rst
+++ b/specs/multiple-globals-files.rst
@@ -36,7 +36,7 @@ more granular control, without the need to add the ``-e @/path/to/file`` flag.
 
 Use cases
 ---------
-1. Allow a more granular controler over individual service's options
+1. Allow a more granular controller over individual service's options
 2. Better file and directory structure
 
 Proposed change
diff --git a/specs/template.rst b/specs/template.rst
index 15a1886af..70c80c2b6 100644
--- a/specs/template.rst
+++ b/specs/template.rst
@@ -45,7 +45,7 @@ Include where in the kolla tree hierarchy this will reside.
 
 Security impact
 ---------------
-How does this feature impact the securtiy of the deployed OpenStack.
+How does this feature impact the security of the deployed OpenStack.
 
 Performance Impact
 ------------------