docs: remove all trailing whitespaces

Done via:
$ find . -name "*.rst" | xargs sed -i 's/[ \t]*$//'

5 files changed, 18 insertions, 18 deletions

diff --git a/docs/services/dns-forwarding.rst b/docs/services/dns-forwarding.rst
index 2ab04707..f28c2d21 100644
--- a/docs/services/dns-forwarding.rst
+++ b/docs/services/dns-forwarding.rst
@@ -28,7 +28,7 @@ Setting a forwarding DNS server for a specific domain:
 .. code-block:: console
 
   set service dns forwarding domain example.com server 192.0.2.1
-  
+
 Set which networks or clients are allowed to query the DNS Server. Allow from all:
 
 .. code-block:: console
@@ -68,5 +68,5 @@ The IP addresses for the LAN interface are 192.168.0.1 and 2001:db8::1
   set service dns forwarding name-server 2001:4860:4860::8888
   set service dns forwarding name-server 2001:4860:4860::8844
   set service dns forwarding listen-address 2001:db8::1
-  set service dns forwarding listen-address 192.168.0.1 
+  set service dns forwarding listen-address 192.168.0.1
   set service dns forwarding allow-from 0.0.0.0/0
diff --git a/docs/services/ipoe-server.rst b/docs/services/ipoe-server.rst
index 1e5e72dc..76a199b4 100644
--- a/docs/services/ipoe-server.rst
+++ b/docs/services/ipoe-server.rst
@@ -26,7 +26,7 @@ Other DHCP discovery requests will be ignored, unless the client mac has been en
   set service ipoe-server interface eth2 client-subnet '192.168.0.0/24'
 
 
-The first address of the parameter ``client-subnet``, will be used as the default gateway. 
+The first address of the parameter ``client-subnet``, will be used as the default gateway.
 Connected sessions can be checked via the ``show ipoe-server sessions`` command.
 
 .. code-block:: console
@@ -59,10 +59,10 @@ IPv6 DNS addresses are optional.
 
 .. code-block:: console
 
-  vyos@ipoe-server# run sh ipoe-server sessions 
-  ifname | called-sid |    calling-sid    |     ip      |               ip6               | ip6-dp          | rate-limit | state  |  uptime  |        sid       
+  vyos@ipoe-server# run sh ipoe-server sessions
+  ifname | called-sid |    calling-sid    |     ip      |               ip6               | ip6-dp          | rate-limit | state  |  uptime  |        sid
   -------+------------+-------------------+-------------+---------------------------------+-----------------+------------+--------+----------+------------------
-  ipoe0  | eth3       | 08:00:27:2f:d8:06 | 192.168.1.2 | 2001:db8::a00:27ff:fe2f:d806/64 | 2001:db8:1::/56 |            | active | 01:02:59 | 4626faf71b12cc25  
+  ipoe0  | eth3       | 08:00:27:2f:d8:06 | 192.168.1.2 | 2001:db8::a00:27ff:fe2f:d806/64 | 2001:db8:1::/56 |            | active | 01:02:59 | 4626faf71b12cc25
 
 
 The clients cpe can now communicate via IPv4 or IPv6. All devices behind ``2001:db8::a00:27ff:fe2f:d806/64`` can use addresses from ``2001:db8:1::/56`` and can
@@ -100,7 +100,7 @@ Bandwidth Shaping
 Bandwidth rate limits can be set for local users within the configuration or via RADIUS based attributes.
 
 
-Bandwidth Shaping for local users 
+Bandwidth Shaping for local users
 =================================
 
 The rate-limit is set in kbit/sec.
@@ -117,9 +117,9 @@ The rate-limit is set in kbit/sec.
 
 .. code-block:: console
 
-  vyos@vyos# run show ipoe-server sessions 
+  vyos@vyos# run show ipoe-server sessions
 
-  ifname | called-sid |    calling-sid    |     ip      | ip6 | ip6-dp | rate-limit | state  |  uptime  |        sid       
+  ifname | called-sid |    calling-sid    |     ip      | ip6 | ip6-dp | rate-limit | state  |  uptime  |        sid
   -------+------------+-------------------+-------------+-----+--------+------------+--------+----------+------------------
   ipoe0  | eth2       | 08:00:27:2f:d8:06 | 192.168.0.2 |     |        | 500/500    | active | 00:00:05 | dccc870fd31349fb
 
diff --git a/docs/services/pppoe-server.rst b/docs/services/pppoe-server.rst
index 3f42ceab..0d2d4e80 100644
--- a/docs/services/pppoe-server.rst
+++ b/docs/services/pppoe-server.rst
@@ -33,9 +33,9 @@ Connections can be locally checked via the command
 .. code-block:: console
 
   show pppoe-server sessions
-  ifname | username |     ip     |    calling-sid    | rate-limit  | state  |  uptime  | rx-bytes | tx-bytes 
+  ifname | username |     ip     |    calling-sid    | rate-limit  | state  |  uptime  | rx-bytes | tx-bytes
   -------+----------+------------+-------------------+-------------+--------+----------+----------+----------
-  ppp0   | foo      | 10.1.1.100 | 08:00:27:ba:db:15 | 20480/10240 | active | 00:00:11 | 214 B    | 76 B     
+  ppp0   | foo      | 10.1.1.100 | 08:00:27:ba:db:15 | 20480/10240 | active | 00:00:11 | 214 B    | 76 B
 
 
 Client IP address pools
@@ -95,7 +95,7 @@ Example, from radius-server send command for disconnect client with username tes
 .. code-block:: console
 
   root@radius-server:~# echo "User-Name=test" | radclient -x 10.1.1.2:3799 disconnect secret123
-  
+
 You can also use another attributes for identify client for disconnect, like Framed-IP-Address, Acct-Session-Id, etc.
 Result commands appears in log
 
@@ -136,7 +136,7 @@ Bandwidth Shaping
 
 Bandwidth rate limits can be set for local users or RADIUS based attributes.
 
-Bandwidth Shaping for local users 
+Bandwidth Shaping for local users
 =================================
 
 The rate-limit is set in kbit/sec.
@@ -209,8 +209,8 @@ The client, once successfully authenticated, will receive an IPv4 and an IPv6 /6
 
 .. code-block:: console
 
-  vyos@pppoe-server:~$ sh pppoe-server sessions 
-   ifname | username |     ip      |            ip6           |       ip6-dp        |    calling-sid    | rate-limit | state  |  uptime  | rx-bytes | tx-bytes 
+  vyos@pppoe-server:~$ sh pppoe-server sessions
+   ifname | username |     ip      |            ip6           |       ip6-dp        |    calling-sid    | rate-limit | state  |  uptime  | rx-bytes | tx-bytes
   --------+----------+-------------+--------------------------+---------------------+-------------------+------------+--------+----------+----------+----------
    ppp0   | test     | 192.168.0.1 | 2001:db8:8002:0:200::/64 | 2001:db8:8003::1/56 | 08:00:27:12:42:eb |            | active | 00:00:49 | 875 B    | 2.1 KiB
 
diff --git a/docs/services/snmp.rst b/docs/services/snmp.rst
index ecb95d1b..2c0d958f 100644
--- a/docs/services/snmp.rst
+++ b/docs/services/snmp.rst
@@ -205,7 +205,7 @@ SNMP Extensions
 ^^^^^^^^^^^^^^^
 
 To extend SNMP agent functionality, custom scripts can be executed every time
-the agent is being called. This can be achieved by using 
+the agent is being called. This can be achieved by using
 ``arbitrary extensioncommands``. The first step is to create a functional
 script of course, then upload it to your VyOS instance via the command
 ``scp your_script.sh vyos@your_router:/config/user-data``.
diff --git a/docs/services/webproxy.rst b/docs/services/webproxy.rst
index 8aca0b85..eaccc4df 100644
--- a/docs/services/webproxy.rst
+++ b/docs/services/webproxy.rst
@@ -105,9 +105,9 @@ Directory as authentication backend. Queries are done via LDAP.
    listen-address 192.168.188.103 {
        disable-transparent
    }
-  
+
 * ``base-dn`` set the base directory for the search
-* ``bind-dn`` and ``password``: set the user, which is used for the ldap search 
+* ``bind-dn`` and ``password``: set the user, which is used for the ldap search
 * ``filter-expression``: set the exact filter which a authorized user match in a ldap-search. In this example every User is able to authorized.
 
 You can find more about the ldap authentication `here <http://www.squid-cache.org/Versions/v3/3.2/manuals/basic_ldap_auth.html>`_