[FIX] *: remove trailing whitespaces

Part-of: odoo/documentation#2983

content/administration/install/deploy.rst

@@ -392,7 +392,7 @@ The solutions to support livechat/motifications in a WSGI application are:
 
 * Deploy a threaded version of Odoo (instead of a process-based preforking
   one) and redirect only requests to URLs starting with ``/websocket/`` to
-  that Odoo, this is the simplest and the websocket URL can double up as the cron 
+  that Odoo, this is the simplest and the websocket URL can double up as the cron
   instance.
 * Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting
   with ``/websocket/`` to
@@ -410,7 +410,7 @@ a static HTTP server.
 Serving static files
 --------------------
 
-Odoo static files are located in each module's :file:`static/` folder, so static files can be served 
+Odoo static files are located in each module's :file:`static/` folder, so static files can be served
 by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module
 (and file) in the various addons paths.
 
@@ -420,13 +420,13 @@ by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up
 
    Using the above NGINX (https) configuration, the following location block should be added to
    serve static files via NGINX.
-   
+
    .. code-block:: nginx
-   
+
        location @odoo {
            # copy-paste the content of the / location block
        }
-   
+
        # Serve static files right away
        location ~ ^/[^/]+/static/.+$ {
            root /usr/lib/python3/dist-packages/odoo/addons;
@@ -444,11 +444,11 @@ by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up
    serve static files via NGINX.
 
    .. code-block:: nginx
-   
+
        location @odoo {
            # copy-paste the content of the / location block
        }
-   
+
        # Serve static files right away
        location ~ ^/[^/]+/static/.+$ {
            root /opt/odoo;
@@ -483,7 +483,7 @@ X-Sendfile and X-Accel).
    - The X-Accel extension for NGINX **does** require the following additionnal configuration:
 
      .. code-block:: nginx
- 
+
          location /web/filestore {
              internal;
              alias /path/to/odoo/data-dir/filestore;

content/administration/maintain/domain_names.rst

@@ -17,7 +17,7 @@ You can use a custom domain name to access your Odoo database and websites:
    ``odoo.com`` for both the URL and the emails (e.g., ``https://example.odoo.com``).
 
 .. important::
-   Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online 
+   Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online
    databases for one year. Visitors can then access your website with an address such as
    ``www.example.com`` rather than the default ``example.odoo.com``.
 

content/administration/maintain/enterprise.rst

@@ -41,7 +41,7 @@ On Linux, using an installer
   .. code-block:: console
 
     $ sudo dpkg -i <path_to_enterprise_deb>
-  
+
 * Update your database to the enterprise packages using
 
   .. code-block:: console

content/administration/maintain/google_oauth.rst

@@ -123,7 +123,7 @@ server in Odoo. The configuration automatically loads the token in Odoo, and a t
    :align: center
    :alt: Configure Outgoing Email Servers in Odoo.
 
-Finally, save the settings and :guilabel:`Test the Connection`. A confirmation message should 
+Finally, save the settings and :guilabel:`Test the Connection`. A confirmation message should
 appear. The Odoo database can now send safe, secure emails through Google using OAuth
 authentication.
 

content/administration/odoo_sh/getting_started/branches.rst

@@ -259,16 +259,16 @@ This server only keeps one month of backups: 7 daily and 4 weekly backups.
 Dedicated backup servers keep the same backups, as well as 3 additional monthly backups.
 To restore or download one of these monthly backups, please `contact us <https://www.odoo.com/help>`_.
 
-If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python 
-dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list), 
-as either the container will be changed by the installation of new pip packages, either the database itself will be 
-changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially 
+If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
+dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
+as either the container will be changed by the installation of new pip packages, either the database itself will be
+changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
 break things.
 
-If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done 
-by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course, 
-as an extra precaution, you can make a backup manually before making big changes in your production sources in case 
-something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups 
+If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
+by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
+as an extra precaution, you can make a backup manually before making big changes in your production sources in case
+something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
 to 5 per day.
 
 The *import database* feature accepts database archives in the format provided by: