git.iko.soy/searx
on master help sign in
[doc] fix small mistakes in engine overview
commit3f11e9d0e5bd81e8a957a47155299b921b986286 authorNoemi Vanyi <sitbackandwait@gmail.com> dateThu 10 Dec 2015, 21:38 (11 years ago) parentbcd6825
3 files changed+6−6
compare with master
unifiedsplit
_sources/dev/engine_overview.txt+2−2 dev/engine_overview.html+2−2 docs/dev/engine_overview.rst+2−2
_sources/dev/engine_overview.txt+2−2
@@ -23,7 +23,7 @@ arguments can be set in the engine file or in the settings file
2323(normally ``settings.yml``). The arguments in the settings file override
2424the ones in the engine file.
2525
26−It does not matter if an options is stored in the engine file or in the
26+It does not matter if an option is stored in the engine file or in the
2727settings. However, the standard way is the following:
2828
2929
@@ -63,7 +63,7 @@ often overwritten by the settings. If ``None`` is assigned to an option
6363in the engine file, it has to be redefined in the settings,
6464otherwise searx will not start with that engine.
6565
66−The naming of that overrides is arbitrary. But the recommended
66+The naming of overrides is arbitrary. But the recommended
6767overrides are the following:
6868
6969+-----------------------+----------+----------------------------------------------------------------+
dev/engine_overview.html+2−2
@@ -82,7 +82,7 @@ external search engines. Adapters are stored under the folder
8282arguments can be set in the engine file or in the settings file
8383(normally <code class="docutils literal"><span class="pre">settings.yml</span></code>). The arguments in the settings file override
8484the ones in the engine file.</p>
85−<p>It does not matter if an options is stored in the engine file or in the
85+<p>It does not matter if an option is stored in the engine file or in the
8686settings. However, the standard way is the following:</p>
8787<div class="section" id="engine-file">
8888<h3><a class="toc-backref" href="#id4">engine file</a><a class="headerlink" href="#engine-file" title="Permalink to this headline">¶</a></h3>
@@ -154,7 +154,7 @@ settings. However, the standard way is the following:</p>
154154often overwritten by the settings. If <code class="docutils literal"><span class="pre">None</span></code> is assigned to an option
155155in the engine file, it has to be redefined in the settings,
156156otherwise searx will not start with that engine.</p>
157−<p>The naming of that overrides is arbitrary. But the recommended
157+<p>The naming of overrides is arbitrary. But the recommended
158158overrides are the following:</p>
159159<table border="1" class="docutils">
160160<colgroup>
docs/dev/engine_overview.rst+2−2
@@ -23,7 +23,7 @@ arguments can be set in the engine file or in the settings file
2323(normally ``settings.yml``). The arguments in the settings file override
2424the ones in the engine file.
2525
26−It does not matter if an options is stored in the engine file or in the
26+It does not matter if an option is stored in the engine file or in the
2727settings. However, the standard way is the following:
2828
2929
@@ -63,7 +63,7 @@ often overwritten by the settings. If ``None`` is assigned to an option
6363in the engine file, it has to be redefined in the settings,
6464otherwise searx will not start with that engine.
6565
66−The naming of that overrides is arbitrary. But the recommended
66+The naming of overrides is arbitrary. But the recommended
6767overrides are the following:
6868
6969+-----------------------+----------+----------------------------------------------------------------+