Fix some typos and capitalizations

4 files changed, 9 insertions, 9 deletions

diff --git a/docs/interfaces/dummy.rst b/docs/interfaces/dummy.rst
index 4627d1dc..e452ae73 100644
--- a/docs/interfaces/dummy.rst
+++ b/docs/interfaces/dummy.rst
@@ -13,8 +13,8 @@ you can have as many as you want.
 
 .. hint:: A Dummy interface is always up, thus it could be used for
    management traffic or as source/destination for and :abbr:`IGP (Interior
-   Gateway Protocol)` like :ref:`bgp` so your internal BGP link is not dependant
-   on physical link states and multiple routes can be choosen to the
+   Gateway Protocol)` like :ref:`bgp` so your internal BGP link is not dependent
+   on physical link states and multiple routes can be chosen to the
    destination. A :ref:`dummy-interface` Interface should always be preferred
    over a :ref:`loopback-interface` interface.
 
diff --git a/docs/interfaces/loopback.rst b/docs/interfaces/loopback.rst
index f7519631..e15062cf 100644
--- a/docs/interfaces/loopback.rst
+++ b/docs/interfaces/loopback.rst
@@ -14,8 +14,8 @@ services on your local machine.
 
 .. hint:: A lookback interface is always up, thus it could be used for
    management traffic or as source/destination for and :abbr:`IGP (Interior
-   Gateway Protocol)` like :ref:`bgp` so your internal BGP link is not dependant
-   on physical link states and multiple routes can be choosen to the
+   Gateway Protocol)` like :ref:`bgp` so your internal BGP link is not dependent
+   on physical link states and multiple routes can be chosen to the
    destination. A :ref:`dummy-interface` Interface should always be preferred
    over a :ref:`loopback-interface` interface.
 
diff --git a/docs/interfaces/vxlan.rst b/docs/interfaces/vxlan.rst
index 67dab820..409131e1 100644
--- a/docs/interfaces/vxlan.rst
+++ b/docs/interfaces/vxlan.rst
@@ -31,7 +31,7 @@ may be blocked by the hypervisor.
 
 .. note:: As VyOS is based on Linux and there was no official IANA port assigned
    for VXLAN, VyOS uses a default port of 8472. You can change the port on a
-   per VXLAN interface basis to get it working accross multiple vendors.
+   per VXLAN interface basis to get it working across multiple vendors.
 
 Configuration
 =============
diff --git a/docs/interfaces/wireless.rst b/docs/interfaces/wireless.rst
index 9e3c6cf5..ea766af2 100644
--- a/docs/interfaces/wireless.rst
+++ b/docs/interfaces/wireless.rst
@@ -23,7 +23,7 @@ added the configuration tree, specifying any detected settings (for example,
 its MAC address) and configured to run in monitor mode.
 
 To be able to use the wireless interfaces you will first need to set a
-regulatory domain with the country code of your locaion.
+regulatory domain with the country code of your location.
 
 .. cfgcmd:: set system wifi-regulatory-domain DE
 
@@ -34,7 +34,7 @@ Configuring Access-Point
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
 The following example creates a WAP. When configuring multiple WAP interfaces,
-you must specify unique IP addresses, channels, Network IDs commonly refered
+you must specify unique IP addresses, channels, Network IDs commonly referred
 to as :abbr:`SSID (Service Set Identifier)`, and MAC addresses.
 
 The WAP in this example has the following characteristics:
@@ -281,8 +281,8 @@ The wireless interface identifier can range from wlan0 to wlan999.
 
 .. opcmd:: show interfaces wireless <wlanX> scan
 
-This command is used to retrive information about WAP within the range of your
-wireless interface. This command is usefull on wireless interfaces configured
+This command is used to retrieve information about WAP within the range of your
+wireless interface. This command is useful on wireless interfaces configured
 in station mode.
 
 .. note:: Scanning is not supported on all wireless drivers and wireless