[fix] typos in documentation & messages

docs/dev/contribution_guide.rst

@@ -186,5 +186,5 @@ commit and push:
 
 .. attention::
 
-   If you are working in your own brand, don't forgett to adjust your
+   If you are working in your own brand, don't forget to adjust your
    :ref:`settings brand`.

docs/dev/engines/index.rst

@@ -26,7 +26,7 @@ The :py:obj:`engine_type <searx.enginelib.Engine.engine_type>` of an engine
 determines which :ref:`search processor <searx.search.processors>` is used by
 the engine.
 
-In this section a list of the enignes that are documented is given, a complete
+In this section a list of the engines that are documented is given, a complete
 list of the engines can be found in the source under: :origin:`searx/engines`.
 
 .. _online engines:

docs/dev/engines/online/duckduckgo.rst

@@ -1,8 +1,8 @@
 .. _duckduckgo engines:
 
-=================
-DukcDukGo Engines
-=================
+==================
+DuckDuckGo Engines
+==================
 
 .. contents::
    :depth: 2

docs/dev/lxcdev.rst

@@ -148,7 +148,7 @@ services quite easy.
 In the example above the SearXNG instance in the container is wrapped to
 ``http://n.n.n.140/searxng`` to the HOST system.  Note, on your HOST system, the
 IP of your ``searxng-archlinux`` container is different to this example.  To
-test the instance in the conatiner from outside of the container, in your WEB
+test the instance in the container from outside of the container, in your WEB
 browser on your desktop just open the URL reported in your installation
 
 .. _working in containers:
@@ -255,7 +255,7 @@ With the use of the :ref:`searxng.sh` the SearXNG service was installed as
 With the command above, we stopped the SearXNG uWSGI-App in the archlinux
 container.
 
-The uWSGI-App for the archlinux dsitros is configured in
+The uWSGI-App for the archlinux distros is configured in
 :origin:`utils/templates/etc/uwsgi/apps-archlinux/searxng.ini`, from where at
 least you should attend the settings of ``uid``, ``chdir``, ``env`` and
 ``http``::
@@ -272,7 +272,7 @@ shares the root folder of the repository and the command ``utils/lxc.sh cmd``
 handles relative path names **transparent**.
 
 To wrap the SearXNG installation in the container into a developer one, we
-simple have to create a smylink to the **transparent** reposetory from the
+simple have to create a symlink to the **transparent** repository from the
 desktop.  Now lets replace the repository at ``searxng-src`` in the container
 with the working tree from outside of the container:
 

docs/dev/makefile.rst

@@ -138,7 +138,7 @@ from the YAML configuration:
 - ``SEARXNG_PORT`` from :ref:`server.port <settings server>`
 
 The ``GIT_URL`` and ``GIT_BRANCH`` in the origin:`utils/brand.env` file, are
-readed from the git VCS and the branch that is checked out when ``make
+read from the git VCS and the branch that is checked out when ``make
 buildenv`` command runs.
 
 .. _brand:
@@ -423,7 +423,7 @@ To get live builds while modifying CSS & JS use (:ref:`make run`):
 
 The :origin:`Makefile` targets ``static.build.*`` cover common tasks to build (a
 commit of) the static files.  The ``./manage static.build..*`` command line
-can be used to convenient run common build tasks of the satic files.
+can be used to convenient run common build tasks of the static files.
 
 .. program-output:: bash -c "cd ..; ./manage static.help"
 

docs/dev/quickstart.rst

@@ -67,14 +67,14 @@ the modified source code from the build products first run:
    make static.build.restore
 
 This will restore the old build products and only your changes of the code
-remain in the working tree which can now be added & commited.  When all sources
-are commited, you can commit the build products simply by:
+remain in the working tree which can now be added & committed.  When all sources
+are committed, you can commit the build products simply by:
 
 .. code:: bash
 
    make static.build.commit
 
-Commiting the build products should be the last step, just before you send us
+Committing the build products should be the last step, just before you send us
 your PR.  There is also a make target to rewind this last build commit:
 
 .. code:: bash

docs/dev/translation.rst

@@ -56,7 +56,7 @@ Sync from *origin* to *weblate*: using ``make weblate.push.translations``
   <.github/workflows/integration.yml>` checks for updated translations.
 
 Sync from *weblate* to *origin*: using ``make weblate.translations.commit``
-  Every Friday, the GitHub workflow :origin:`babel / create PR for additons from
+  Every Friday, the GitHub workflow :origin:`babel / create PR for additions from
   weblate <.github/workflows/translations-update.yml>` creates a PR with the
   updated translation files: