don't even try heavily penalized searches

[nominatim.git] / docs / develop / ICU-Tokenizer-Modules.md

diff --git a/docs/develop/ICU-Tokenizer-Modules.md b/docs/develop/ICU-Tokenizer-Modules.md
index f1853006f00400ed772126a10a4901e1550bd0eb..daadf8998ac7a40cddf4a008ebb499bbb0f34883 100644 (file)
--- a/docs/develop/ICU-Tokenizer-Modules.md
+++ b/docs/develop/ICU-Tokenizer-Modules.md
@@ -54,7 +54,7 @@ the function.
 
 ::: nominatim.tokenizer.sanitizers.config.SanitizerConfig
     options:
-        heading_level: 3
+        heading_level: 6
 
 ### The main filter function of the sanitizer
 
@@ -75,14 +75,14 @@ adding extra attributes) or completely replace the list with a different one.
 
 ::: nominatim.data.place_info.PlaceInfo
     options:
-        heading_level: 3
+        heading_level: 6
 
 
 #### PlaceName - extended naming information
 
 ::: nominatim.data.place_name.PlaceName
     options:
-        heading_level: 3
+        heading_level: 6
 
 
 ### Example: Filter for US street prefixes
@@ -129,7 +129,7 @@ sanitizers:
 !!! warning
     This example is just a simplified show case on how to create a sanitizer.
     It is not really read for real-world use: while the sanitizer would
-    correcly transform `West 5th Street` into `5th Street`. it would also
+    correctly transform `West 5th Street` into `5th Street`. it would also
     shorten a simple `North Street` to `Street`.
 
 For more sanitizer examples, have a look at the sanitizers provided by Nominatim.
@@ -141,12 +141,12 @@ They can be found in the directory
 
 ::: nominatim.tokenizer.token_analysis.base.AnalysisModule
     options:
-        heading_level: 3
+        heading_level: 6
 
 
 ::: nominatim.tokenizer.token_analysis.base.Analyzer
     options:
-        heading_level: 3
+        heading_level: 6
 
 ### Example: Creating acronym variants for long names