[furo] remove .. contents:: directives (#3408)

The directive creates a table of contents for the page.  However, Furo includes
a table of contents already in the sidebar.  It is, thus, recommended to
removing the `.. contents::` directive.

[1] https://github.com/pradyunsg/furo/issues/88#issuecomment-803297274

Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>

docs/admin/buildhosts.rst

@@ -4,11 +4,6 @@
 Buildhosts
 ==========
 
-.. contents::
-   :depth: 2
-   :local:
-   :backlinks: entry
-
 To get best results from build, it's recommend to install additional packages on
 build hosts (see :ref:`searxng.sh`).
 

docs/admin/installation-apache.rst

@@ -61,11 +61,6 @@ section might give you some guidance.
    - `Apache Fedora`_
    - `Apache directives`_
 
-.. contents::
-   :depth: 2
-   :local:
-   :backlinks: entry
-
 
 The Apache HTTP server
 ======================

docs/admin/installation-nginx.rst

@@ -41,12 +41,6 @@ section might give you some guidance.
    - `uWSGI support from nginx`_
 
 
-.. contents::
-   :depth: 2
-   :local:
-   :backlinks: entry
-
-
 The nginx HTTP server
 =====================
 

docs/admin/installation-searxng.rst

@@ -4,12 +4,6 @@
 Step by step installation
 =========================
 
-.. contents::
-   :depth: 2
-   :local:
-   :backlinks: entry
-
-
 In this section we show the setup of a SearXNG instance that will be installed
 by the :ref:`installation scripts`.
 

docs/admin/installation-uwsgi.rst

@@ -9,12 +9,6 @@ uWSGI
    - `systemd.unit`_
    - `uWSGI Emperor`_
 
-.. contents::
-   :depth: 2
-   :local:
-   :backlinks: entry
-
-
 .. _systemd.unit: https://www.freedesktop.org/software/systemd/man/systemd.unit.html
 .. _One service per app in systemd:
     https://uwsgi-docs.readthedocs.io/en/latest/Systemd.html#one-service-per-app-in-systemd

docs/admin/searx.favicons.rst

@@ -8,11 +8,6 @@ Favicons
 
    Don't activate the favicons before reading the documentation.
 
-.. contents::
-   :depth: 2
-   :local:
-   :backlinks: entry
-
 Activating the favicons in SearXNG is very easy, but this **generates a
 significantly higher load** in the client/server communication and increases
 resources needed on the server.
@@ -250,4 +245,3 @@ into the *proxy*:
 .. _data URL:
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URLs
 .. _FQN: https://en.wikipedia.org/wiki/Fully_qualified_name
-

docs/admin/searx.limiter.rst

@@ -8,10 +8,5 @@ Limiter
 
    The limiter requires a :ref:`Valkey <settings valkey>` database.
 
-.. contents::
-   :depth: 2
-   :local:
-   :backlinks: entry
-
 .. automodule:: searx.limiter
    :members:

docs/admin/settings/settings.rst

@@ -12,11 +12,6 @@ file.
    - :ref:`use_default_settings.yml`
    - :ref:`search API`
 
-.. contents::
-   :depth: 2
-   :local:
-   :backlinks: entry
-
 .. _settings location:
 
 settings.yml location

docs/admin/update-searxng.rst

@@ -9,11 +9,6 @@ SearXNG maintenance
    - :ref:`toolboxing`
    - :ref:`uWSGI maintenance`
 
-.. contents::
-   :depth: 2
-   :local:
-   :backlinks: entry
-
 .. _update searxng:
 
 How to update