diff --git a/_sources/dev/engine_overview.txt b/_sources/dev/engine_overview.txt
index 05a54b64..186cc0f9 100644
--- a/_sources/dev/engine_overview.txt
+++ b/_sources/dev/engine_overview.txt
@@ -23,7 +23,7 @@ arguments can be set in the engine file or in the settings file
(normally ``settings.yml``). The arguments in the settings file override
the ones in the engine file.
-It does not matter if an options is stored in the engine file or in the
+It does not matter if an option is stored in the engine file or in the
settings. However, the standard way is the following:
@@ -63,7 +63,7 @@ often overwritten by the settings. If ``None`` is assigned to an option
in the engine file, it has to be redefined in the settings,
otherwise searx will not start with that engine.
-The naming of that overrides is arbitrary. But the recommended
+The naming of overrides is arbitrary. But the recommended
overrides are the following:
+-----------------------+----------+----------------------------------------------------------------+
diff --git a/dev/engine_overview.html b/dev/engine_overview.html
index fe559091..f77cd515 100644
--- a/dev/engine_overview.html
+++ b/dev/engine_overview.html
@@ -82,7 +82,7 @@ external search engines. Adapters are stored under the folder
arguments can be set in the engine file or in the settings file
(normally settings.yml
). The arguments in the settings file override
the ones in the engine file.
It does not matter if an options is stored in the engine file or in the +
It does not matter if an option is stored in the engine file or in the settings. However, the standard way is the following:
None
is assigned to an option
in the engine file, it has to be redefined in the settings,
otherwise searx will not start with that engine.
-The naming of that overrides is arbitrary. But the recommended +
The naming of overrides is arbitrary. But the recommended overrides are the following: