service: Corrected spelling mistakes

5 files changed, 9 insertions, 9 deletions

diff --git a/docs/configuration/service/broadcast-relay.rst b/docs/configuration/service/broadcast-relay.rst
index b6e2bed7..f64bb208 100644
--- a/docs/configuration/service/broadcast-relay.rst
+++ b/docs/configuration/service/broadcast-relay.rst
@@ -20,7 +20,7 @@ Configuration
 .. cfgcmd:: set service broadcast-relay id <n> description <description>
 
    A description can be added for each and every unique relay ID. This is
-   useful to distinguish between multiple different ports/appliactions.
+   useful to distinguish between multiple different ports/applications.
 
 .. cfgcmd:: set service broadcast-relay id <n> interface <interface>
 
@@ -35,7 +35,7 @@ Configuration
 
 .. cfgcmd:: set service broadcast-relay id <n> port <port>
 
-   The UDP port number used by your apllication. It is mandatory for this kind
+   The UDP port number used by your application. It is mandatory for this kind
    of operation.
 
 .. cfgcmd:: set service broadcast-relay id <n> disable
diff --git a/docs/configuration/service/conntrack-sync.rst b/docs/configuration/service/conntrack-sync.rst
index db23c92f..232db1a8 100644
--- a/docs/configuration/service/conntrack-sync.rst
+++ b/docs/configuration/service/conntrack-sync.rst
@@ -29,7 +29,7 @@ will be mandatorily defragmented.
 
 It is possible to use either Multicast or Unicast to sync conntrack traffic.
 Most examples below show Multicast, but unicast can be specified by using the
-"peer" keywork after the specificed interface, as in the following example:
+"peer" keywork after the specified interface, as in the following example:
 
 :cfgcmd:`set service conntrack-sync interface eth0 peer 192.168.0.250`
 
@@ -204,7 +204,7 @@ Now configure conntrack-sync service on ``router1`` **and** ``router2``
 
 .. code-block:: none
 
-  set high-availablilty vrrp group internal virtual-address ... etc ...
+  set high-availability vrrp group internal virtual-address ... etc ...
   set high-availability vrrp sync-group syncgrp member 'internal'
   set service conntrack-sync accept-protocol 'tcp'
   set service conntrack-sync accept-protocol 'udp'
diff --git a/docs/configuration/service/ids.rst b/docs/configuration/service/ids.rst
index 3e508d50..8a64467f 100644
--- a/docs/configuration/service/ids.rst
+++ b/docs/configuration/service/ids.rst
@@ -33,7 +33,7 @@ Configuration
     Configure direction for processing traffic. 
 
 .. cfgcmd:: set service ids ddos-protection exclude-network <x.x.x.x/x>
-.. cfgcmd:: set service ids ddos-protection exlude-network <h:h:h:h:h:h:h:h/x>
+.. cfgcmd:: set service ids ddos-protection exclude-network <h:h:h:h:h:h:h:h/x>
 
     Specify IPv4 and/or IPv6 networks which are going to be excluded.
 
@@ -56,7 +56,7 @@ Configuration
 
 .. cfgcmd:: set service ids ddos-protection sflow port <1-65535>
 
-    Configure port number to be used for sflow conection. Default port is 6343.
+    Configure port number to be used for sflow connection. Default port is 6343.
 
 .. cfgcmd:: set service ids ddos-protection threshold general
    [fps | mbps | pps] <0-4294967294>
@@ -96,7 +96,7 @@ In this simplified scenario, main things to be considered are:
     * Interface **eth0** used to connect to upstream.
 
 Since we are analyzing attacks to and from our internal network, two types
-of attacks can be identified, and differents actions are needed:
+of attacks can be identified, and different actions are needed:
 
     * External attack: an attack from the internet towards an internal IP
       is identify. In this case, all connections towards such IP will be
diff --git a/docs/configuration/service/router-advert.rst b/docs/configuration/service/router-advert.rst
index ca558b6a..8f984b10 100644
--- a/docs/configuration/service/router-advert.rst
+++ b/docs/configuration/service/router-advert.rst
@@ -38,7 +38,7 @@ Configuration
    "Cur Hop Limit", "hop-limit", "Hop count field of the outgoing RA packets"
    """Managed address configuration"" flag", "managed-flag", "Tell hosts to use the administered stateful protocol (i.e. DHCP) for autoconfiguration"
    """Other configuration"" flag", "other-config-flag", "Tell hosts to use the administered (stateful) protocol (i.e. DHCP) for autoconfiguration of other (non-address) information"
-   "MTU","link-mtu","Link MTU value placed in RAs, exluded in RAs if unset"
+   "MTU","link-mtu","Link MTU value placed in RAs, excluded in RAs if unset"
    "Router Lifetime","default-lifetime","Lifetime associated with the default router in units of seconds"
    "Reachable Time","reachable-time","Time, in milliseconds, that a node assumes a neighbor is reachable after having received a reachability confirmation"
    "Retransmit Timer","retrans-timer","Time in milliseconds between retransmitted Neighbor Solicitation messages"
diff --git a/docs/configuration/service/salt-minion.rst b/docs/configuration/service/salt-minion.rst
index aa747c36..8638246b 100644
--- a/docs/configuration/service/salt-minion.rst
+++ b/docs/configuration/service/salt-minion.rst
@@ -17,7 +17,7 @@ Requirements
 ************
 
 To use the Salt-Minion, a running Salt-Master is required. You can find more
-in the `Salt Poject Documentaion
+in the `Salt Project Documentation
 <https://docs.saltproject.io/en/latest/contents.html>`_
 
 *************