[brand] docs - normalize project name to SearXNG

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

docs/dev/offline_engines.rst

@@ -11,7 +11,7 @@ Offline Engines
    - :ref:`engine command`
    - :origin:`Redis <searx/engines/redis_server.py>`
 
-To extend the functionality of SearxNG, offline engines are going to be
+To extend the functionality of SearXNG, offline engines are going to be
 introduced.  An offline engine is an engine which does not need Internet
 connection to perform a search and does not use HTTP to communicate.
 
@@ -47,14 +47,14 @@ Engine representation in ``/config``
 Extra Dependencies
 ==================
 
-If an offline engine depends on an external tool, SearxNG does not install it by
+If an offline engine depends on an external tool, SearXNG does not install it by
 default.  When an administrator configures such engine and starts the instance,
 the process returns an error with the list of missing dependencies.  Also,
 required dependencies will be added to the comment/description of the engine, so
 admins can install packages in advance.
 
 If there is a need to install additional packages in *Python's Virtual
-Environment* of your SearxNG instance you need to switch into the environment
+Environment* of your SearXNG instance you need to switch into the environment
 (:ref:`searx-src`) first, for this you can use :ref:`searx.sh`::
 
   $ sudo utils/searx.sh shell
@@ -66,7 +66,7 @@ Private engines (Security)
 
 To limit the access to offline engines, if an instance is available publicly,
 administrators can set token(s) for each of the :ref:`private engines`.  If a
-query contains a valid token, then SearxNG performs the requested private
+query contains a valid token, then SearXNG performs the requested private
 search.  If not, requests from an offline engines return errors.