HSEARCH-2584 Move the listing of built-in normalizers to separate sec…

…tions

Signed-off-by: Yoann Rodière <yoann@hibernate.org>

documentation/src/main/asciidoc/reference/backend-elasticsearch.asciidoc

@@ -750,10 +750,10 @@ only definitions from the specific configurer will be taken into account.
 ====
 
 [[backend-elasticsearch-analysis-builtin]]
-=== Built-in analyzers and normalizers
+=== Built-in analyzers
 
-Built-in analyzers and normalizers are available out-of-the-box and don't require explicit configuration.
-If necessary, they can be overridden by defining your own analyzer/normalizer with the same name.
+Built-in analyzers are available out-of-the-box and don't require explicit configuration.
+If necessary, they can be overridden by defining your own analyzer with the same name.
 
 The Elasticsearch backend comes with several built-in analyzers.
 The exact list depends on the version of Elasticsearch and can be found
@@ -763,6 +763,9 @@ One important built-in analyzer is the one named `default`:
 it is used by default with <<mapper-orm-directfieldmapping-annotations-fulltextfield,`@FullTextField`>>.
 Unless overridden explicitly, this analyzer uses a `standard` tokenizer and a `lowercase` filter.
 
+[[backend-elasticsearch-analysis-builtin-normalizer]]
+=== Built-in normalizers
+
 The Elasticsearch backend does not provide any built-in normalizer.
 
 [[backend-elasticsearch-analysis-analyzers]]

documentation/src/main/asciidoc/reference/backend-lucene.asciidoc

@@ -571,7 +571,7 @@ to only return search hits for the current tenant.
 both when indexing (document processing)
 and when searching (query processing).
 
-The Lucene backend comes with some <<backend-lucene-analysis-builtin,defaults>>,
+The Lucene backend comes with some <<backend-lucene-analysis-builtin,default analyzers>>,
 but analysis also be configured explicitly.
 
 To configure analysis in a Lucene backend, you will need to:
@@ -587,10 +587,10 @@ and the configurer will be able to take advantage of a DSL to define
 See below for examples.
 
 [[backend-lucene-analysis-builtin]]
-=== Built-in analyzers and normalizers
+=== Built-in analyzers
 
-Built-in analyzers and normalizers are available out-of-the-box and don't require explicit configuration.
-If necessary, they can be overridden by defining your own analyzer/normalizer with the same name.
+Built-in analyzers are available out-of-the-box and don't require explicit configuration.
+If necessary, they can be overridden by defining your own analyzer with the same name.
 
 The Lucene backend comes with a series of built-in analyzer:
 
@@ -634,6 +634,9 @@ but with fewer features: no terms aggregations, for example.
 +
 Consider using a <<mapper-orm-directfieldmapping-annotations-keywordfield,`@KeywordField`>> instead.
 
+[[backend-lucene-analysis-builtin-normalizer]]
+=== Built-in normalizers
+
 The Lucene backend does not provide any built-in normalizer.
 
 [[backend-lucene-analysis-analyzers]]