Clean up some minor spelling and typos.

Signed-off-by: Justin Pettit <jpettit@ovn.org>
Acked-by: Ben Pfaff <blp@ovn.org>

5 files changed, 12 insertions, 12 deletions

diff --git a/Documentation/howto/docker.rst b/Documentation/howto/docker.rst
index ff8b708af..a68b02fdb 100644
--- a/Documentation/howto/docker.rst
+++ b/Documentation/howto/docker.rst
@@ -43,7 +43,7 @@ Setup
 -----
 
 For multi-host networking with OVN and Docker, Docker has to be started with a
-destributed key-value store. For example, if you decide to use consul as your
+distributed key-value store. For example, if you decide to use consul as your
 distributed key-value store and your host IP address is ``$HOST_IP``, start
 your Docker daemon with::
 
@@ -120,7 +120,7 @@ The "overlay" mode
      The options are ``geneve`` or ``stt``. Your kernel must have support for
      your chosen ``$ENCAP_TYPE``. Both ``geneve`` and ``stt`` are part of the
      Open vSwitch kernel module that is compiled from this repo. If you use the
-     Open vSwitch kernel module from upstream Linux, you will need a minumum
+     Open vSwitch kernel module from upstream Linux, you will need a minimum
      kernel version of 3.18 for ``geneve``. There is no ``stt`` support in
      upstream Linux. You can verify whether you have the support in your kernel
      as follows::
@@ -322,5 +322,5 @@ The "underlay" mode
 From here-on you can use the same Docker commands as described in
 `docker-overlay`_.
 
-Refer the the ovs-architecture man pages (``man ovn-architecture``) to
+Refer to the ovs-architecture man pages (``man ovn-architecture``) to
 understand OVN's architecture in detail.
diff --git a/Documentation/howto/dpdk.rst b/Documentation/howto/dpdk.rst
index d717d2ebe..79b626c76 100644
--- a/Documentation/howto/dpdk.rst
+++ b/Documentation/howto/dpdk.rst
@@ -337,10 +337,10 @@ performance of non-tunnel traffic, specifically for smaller size packet.
 Extended & Custom Statistics
 ----------------------------
 
-DPDK Extended Statistics API allows PMD to expose unique set of statistics.
-The Extended statistics are implemented and supported only for DPDK physical
-and vHost ports. Custom statistics are dynamic set of counters which can
-vary depenend on a driver. Those statistics are implemented
+DPDK Extended Statistics API allows PMD to expose a unique set of statistics.
+The Extended Statistics are implemented and supported only for DPDK physical
+and vHost ports. Custom statistics are a dynamic set of counters which can
+vary depending on the driver. Those statistics are implemented
 for DPDK physical ports and contain all "dropped", "error" and "management"
 counters from XSTATS. XSTATS counters list can be found here:
 <https://wiki.opnfv.org/display/fastpath/Collectd+Metrics+and+Events>`__.
@@ -508,7 +508,7 @@ Add a userspace bridge and two ``dpdk`` (PHY) ports::
     $ ovs-vsctl add-port br0 phy1 -- set Interface phy1 type=dpdk
           options:dpdk-devargs=0000:01:00.1 ofport_request=2
 
-Add test flows to forward packets betwen DPDK port 0 and port 1::
+Add test flows to forward packets between DPDK port 0 and port 1::
 
     # Clear current flows
     $ ovs-ofctl del-flows br0
@@ -543,7 +543,7 @@ ports::
     $ ovs-vsctl add-port br0 dpdkvhostuser1 \
         -- set Interface dpdkvhostuser1 type=dpdkvhostuser ofport_request=4
 
-Add test flows to forward packets betwen DPDK devices and VM ports::
+Add test flows to forward packets between DPDK devices and VM ports::
 
     # Clear current flows
     $ ovs-ofctl del-flows br0
diff --git a/Documentation/howto/firewalld.rst b/Documentation/howto/firewalld.rst
index b76a4d2b7..0dc455ea8 100644
--- a/Documentation/howto/firewalld.rst
+++ b/Documentation/howto/firewalld.rst
@@ -77,7 +77,7 @@ Variations
 
 When installing the XML service files, you have the choice of copying them to
 ``/etc/firewalld/services`` or ``/usr/lib/firewalld/services``. The former is
-recommened since the latter can be overwritten if firewalld is upgraded.
+recommend since the latter can be overwritten if firewalld is upgraded.
 
 The above commands assumed your underlay network interfaces are in the
 "public" firewalld zone. If your underlay network interfaces are in a separate
diff --git a/Documentation/howto/lisp.rst b/Documentation/howto/lisp.rst
index a65a694c7..f9a329eff 100644
--- a/Documentation/howto/lisp.rst
+++ b/Documentation/howto/lisp.rst
@@ -57,7 +57,7 @@ VMs), or have the hypervisor do proxy ARP.  In this scenario, the eth0
 interfaces need not be added to the br0 bridge in the examples below.
 
 On the receiving side, the packet arrives without the original MAC header.  The
-LISP tunneling code attaches a header with harcoded source and destination MAC
+LISP tunneling code attaches a header with hard-coded source and destination MAC
 address ``02:00:00:00:00:00``.  This address has all bits set to 0, except the
 locally administered bit, in order to avoid potential collisions with existing
 allocations.  In order for packets to reach their intended destination, the
diff --git a/Documentation/howto/userspace-tunneling.rst b/Documentation/howto/userspace-tunneling.rst
index 6ad97daec..d0a767bbc 100644
--- a/Documentation/howto/userspace-tunneling.rst
+++ b/Documentation/howto/userspace-tunneling.rst
@@ -80,7 +80,7 @@ should be running before proceeding.
 Configuration Steps
 -------------------
 
-Perform the folowing configuration on `host1`:
+Perform the following configuration on `host1`:
 
 #. Create a ``br-int`` bridge::