[brand] searxng -- fix links to issue tracker & WEB-GUI

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

5 files changed, 7 insertions, 7 deletions

diff --git a/docs/blog/command-line-engines.rst b/docs/blog/command-line-engines.rst
index 746c9e4ae..09eb84fb4 100644
--- a/docs/blog/command-line-engines.rst
+++ b/docs/blog/command-line-engines.rst
@@ -10,7 +10,7 @@ connecting to any networks from the same graphical user interface.
 Command line engines
 ====================
 
-In :pull:`2128` a new type of engine has been introduced called ``command``.
+In :pull-searx:`2128` a new type of engine has been introduced called ``command``.
 This engine lets administrators add engines which run arbitrary shell commands
 and show its output on the web UI of searx.
 
diff --git a/docs/blog/intro-offline.rst b/docs/blog/intro-offline.rst
index f6e90de3a..3a706d038 100644
--- a/docs/blog/intro-offline.rst
+++ b/docs/blog/intro-offline.rst
@@ -56,7 +56,7 @@ As offline searches can return arbitrary results depending on the engine, the
 current result templates were insufficient to present such results.  Thus, a new
 template is introduced which is caplable of presenting arbitrary key value pairs
 as a table. You can check out the pull request for more details see
-:pull:`1700`.
+:pull-searx:`1700`.
 
 Next steps
 ==========
diff --git a/docs/blog/lxcdev-202006.rst b/docs/blog/lxcdev-202006.rst
index b53501dab..24d9028c2 100644
--- a/docs/blog/lxcdev-202006.rst
+++ b/docs/blog/lxcdev-202006.rst
@@ -81,7 +81,7 @@ fork:
      .. code:: sh
 
         $ cd ~/Downloads
-        $ git clone https://github.com/searx/searx.git
+        $ git clone https://github.com/searxng/searxng.git searx
         $ cd searx
 
 The :ref:`lxc-searx.env` consists of several images, see ``export
diff --git a/docs/blog/private-engines.rst b/docs/blog/private-engines.rst
index 027cc3dd3..37b1d4cc5 100644
--- a/docs/blog/private-engines.rst
+++ b/docs/blog/private-engines.rst
@@ -12,7 +12,7 @@ would rather share engines only with their trusted friends or colleagues.
 Private engines
 ===============
 
-To solve this issue private engines were introduced in :pull:`1823`.
+To solve this issue private engines were introduced in :pull-searx:`1823`.
 A new option was added to engines named `tokens`. It expects a list
 of strings. If the user making a request presents one of the tokens
 of an engine, they can access information about the engine
@@ -29,7 +29,7 @@ Example configuration to restrict access to the Arch Linux Wiki engine:
 
 
 Unless a user has configured the right token, the engine is going
-to be hidden from him/her. It is not going to be included in the 
+to be hidden from him/her. It is not going to be included in the
 list of engines on the Preferences page and in the output of
 `/config` REST API call.
 
@@ -42,7 +42,7 @@ is not carved in stone. As providing access to such engines
 implies that the admin knows and trusts the user, we do not see
 necessary to come up with a strict process. Instead,
 we would like to add guidelines to the documentation of the feature.
- 
+
 Next steps
 ==========
 
diff --git a/docs/blog/python3.rst b/docs/blog/python3.rst
index 1d2cfc813..7e770c193 100644
--- a/docs/blog/python3.rst
+++ b/docs/blog/python3.rst
@@ -54,7 +54,7 @@ If you found bugs
 Please open an issue on `GitHub`_.  Make sure that you mention your Python
 version in your issue, so we can investigate it properly.
 
-.. _GitHub: https://github.com/searx/searx/issues
+.. _GitHub: https://github.com/searxng/searxng/issues
 
 Acknowledgment
 ==============