diff --git a/doc/source/devref/fluent-logging.rst b/doc/source/devref/fluent-logging.rst
index 171038d098..78e6b0fafd 100644
--- a/doc/source/devref/fluent-logging.rst
+++ b/doc/source/devref/fluent-logging.rst
@@ -25,7 +25,7 @@ each node and mounts the `/var/lib/docker/containers` directory. The Docker
 container runtime engine directs events posted to stdout and stderr to this
 directory on the host. Fluent-bit then forward the contents of that directory to
 Fluentd. Fluentd runs as deployment at the designated nodes and expose service
-for Fluent-bit to foward logs. Fluentd should then apply the Logstash format to
+for Fluent-bit to forward logs. Fluentd should then apply the Logstash format to
 the logs. Fluentd can also write kubernetes and OpenStack metadata to the logs.
 Fluentd will then forward the results to Elasticsearch and to optionally kafka.
 Elasticsearch indexes the logs in a logstash-* index by default. Kafka stores
diff --git a/doc/source/devref/oslo-config.rst b/doc/source/devref/oslo-config.rst
index b2830851d5..f885366ead 100644
--- a/doc/source/devref/oslo-config.rst
+++ b/doc/source/devref/oslo-config.rst
@@ -31,7 +31,7 @@ snippet for an imaginary Keystone configuration is described here:
               - log
         security_compliance:
           password_expires_ignore_user_ids:
-          # Values in a list will be converted to a comma seperated key
+          # Values in a list will be converted to a comma separated key
             - "123"
             - "456"
 
diff --git a/doc/source/install/ext-dns-fqdn.rst b/doc/source/install/ext-dns-fqdn.rst
index ccaec57cef..7c6d710384 100644
--- a/doc/source/install/ext-dns-fqdn.rst
+++ b/doc/source/install/ext-dns-fqdn.rst
@@ -76,7 +76,7 @@ The default FQDN's for OpenStack-Helm are
 
 We want to change the ***public*** configurations to match our DNS layouts above. In each Chart
 ``values.yaml`` is a ``endpoints`` configuration that has ``host_fqdn_override``'s for each API
-that the Chart either produces or is dependant on. `Read more about how Endpoints are developed
+that the Chart either produces or is dependent on. `Read more about how Endpoints are developed
 <https://docs.openstack.org/openstack-helm/latest/devref/endpoints.html>`__.
 Note while Glance Registry is listening on a Ingress http endpoint, you will not need to expose
 the registry for external services.
diff --git a/doc/source/specs/fluentbit-fluentd-architecture.rst b/doc/source/specs/fluentbit-fluentd-architecture.rst
index 18f087259d..c0db2a2b27 100644
--- a/doc/source/specs/fluentbit-fluentd-architecture.rst
+++ b/doc/source/specs/fluentbit-fluentd-architecture.rst
@@ -83,7 +83,7 @@ each node and mounts the /var/lib/docker/containers directory. The Docker
 container runtime engine directs events posted to stdout and stderr to this
 directory on the host. Fluentbit then forward the contents of that directory to
 Fluentd. Fluentd runs as deployment at the designated nodes and expose service
-for Fluentbit to foward logs. Fluentd should then apply the Logstash format to
+for Fluentbit to forward logs. Fluentd should then apply the Logstash format to
 the logs. Fluentd can also write Kubernetes and OpenStack metadata to the logs.
 Fluentd will then forward the results to Elasticsearch and to optionally Kafka.
 Elasticsearch indexes the logs in a logstash-* index by default. Kafka stores