nikon/docsearch
1
0
Fork 0
Code Activity Actions

Fix a set of minor typos in the text (#570)

Browse source 
This commit just fixes a set of minor typos in the text, that I found while reading through it. It also makes a small grammar adjustment as well, for greater reading clarity.
This commit is contained in:
Matthew Setter 2018-12-19 11:19:05 +01:00 committed by Sylvain Pace
parent 2d67a21ae3
commit e5552fac38
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/src/inside-the-engine.md
View file

@ -44,16 +44,16 @@ then fallback to partial matches. Those results will then be ordered based, once
again, on the page hierarchy, as extracted from the `selectors`.
The default strategy is to promote records having matching words in the highest
level fist. Thus if two results have the same matching words, the one having
them in the highest level (lvl0) will be reanked higher. We also use the
level first. Thus if two results have the same matching words, the one having
them in the highest level (lvl0) will be ranked higher. We also use the
position of the matching words. The sooner they appear within the HTML flow, the
higher the record will be ranked.
The relevancy is based on several factors and can be customized according to the
Algolia tie-breaking method.
You can boost pages depending ont their URLs. This is done from the `start_urls`
and its `page_rank` attributes. It is a numeric value, default to 0. The higher
You can boost pages depending on their URLs. This is done from the `start_urls`
and its `page_rank` attributes. It is a numeric value (defaults to 0). The higher
it is, the higher results from the matching pages will be ranked. For example
all pages with a `page_rank` of 5 will be returned before pages with a
`page_rank` of 1.