mirror of https://github.com/searx/searx
[doc] fix small mistakes in engine overview
This commit is contained in:
parent
bcd6825fdc
commit
3f11e9d0e5
|
@ -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:
|
||||
|
||||
+-----------------------+----------+----------------------------------------------------------------+
|
||||
|
|
|
@ -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 <code class="docutils literal"><span class="pre">settings.yml</span></code>). The arguments in the settings file override
|
||||
the ones in the engine file.</p>
|
||||
<p>It does not matter if an options is stored in the engine file or in the
|
||||
<p>It does not matter if an option is stored in the engine file or in the
|
||||
settings. However, the standard way is the following:</p>
|
||||
<div class="section" id="engine-file">
|
||||
<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>
|
|||
often overwritten by the settings. If <code class="docutils literal"><span class="pre">None</span></code> 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.</p>
|
||||
<p>The naming of that overrides is arbitrary. But the recommended
|
||||
<p>The naming of overrides is arbitrary. But the recommended
|
||||
overrides are the following:</p>
|
||||
<table border="1" class="docutils">
|
||||
<colgroup>
|
||||
|
|
|
@ -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:
|
||||
|
||||
+-----------------------+----------+----------------------------------------------------------------+
|
||||
|
|
Loading…
Reference in New Issue