explicitely->explicitly

This commit is contained in:
Jean-Francois Dockes
2019-12-02 10:42:53 +01:00
parent 94b67520c4
commit 34bdc4d19e
7 changed files with 36 additions and 23 deletions
+4 -4
View File
@@ -1526,7 +1526,7 @@ Chapter 3. Searching
The search will only propose replacement terms with spelling variations
when no matching document were found. In some cases, both proper spellings
and mispellings are present in the index, and it may be interesting to
look for them explicitely.
look for them explicitly.
The term explorer tool (started from the toolbar icon or from the Term
explorer entry of the Tools menu) can be used to search the full index
@@ -1795,7 +1795,7 @@ Chapter 3. Searching
Both simple and advanced query dialogs save recent history, but the amount
is limited: old queries will eventually be forgotten. Also, important
queries may be difficult to find among others. This is why both types of
queries can also be explicitely saved to files, from the GUI menus: File
queries can also be explicitly saved to files, from the GUI menus: File
-> Save last query / Load last query
The default location for saved queries is a subdirectory of the current
@@ -2502,7 +2502,7 @@ Chapter 3. Searching
As in the past, capitalizing the first letter of a word will turn off its
stem expansion and have no effect on case-sensitivity.
You can also explicitely activate case and diacritics sensitivity by using
You can also explicitly activate case and diacritics sensitivity by using
modifiers with the query language. C will make the term case-sensitive,
and D will make it diacritics-sensitive. Examples:
@@ -3817,7 +3817,7 @@ Chapter 5. Installation and configuration
The values in the *skippedPaths variables are matched by default
with fnmatch(3), with the FNM_PATHNAME flag. This means that '/'
characters must be matched explicitely. You can set
characters must be matched explicitly. You can set
skippedPathsFnmPathname to 0 to disable the use of FNM_PATHNAME
(meaning that /*/dir3 will match /dir1/dir2/dir3).