From 3f11e9d0e5bd81e8a957a47155299b921b986286 Mon Sep 17 00:00:00 2001 From: Noemi Vanyi Date: Thu, 10 Dec 2015 21:38:39 +0100 Subject: [PATCH] [doc] fix small mistakes in engine overview --- _sources/dev/engine_overview.txt | 4 ++-- dev/engine_overview.html | 4 ++-- docs/dev/engine_overview.rst | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) 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:

engine fileΒΆ

@@ -154,7 +154,7 @@ settings. However, the standard way is the following:

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/docs/dev/engine_overview.rst b/docs/dev/engine_overview.rst index 05a54b64..186cc0f9 100644 --- a/docs/dev/engine_overview.rst +++ b/docs/dev/engine_overview.rst @@ -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: +-----------------------+----------+----------------------------------------------------------------+