Improve documentation for Linear Top Level Normalizer

docs/reference/elasticsearch/rest-apis/retrievers/linear-retriever.md

@@ -37,10 +37,7 @@ Combining `query` and `retrievers` is not supported.
 
     When used with the [multi-field query format](../retrievers.md#multi-field-query-format) (`query` parameter), normalizes scores per [field grouping](../retrievers.md#multi-field-field-grouping).
     Otherwise serves as the default normalizer for any sub-retriever that doesn't specify its own normalizer. Per-retriever normalizers always take precedence over the top-level normalizer.
-
-    :::{note}
-    **Top-level normalizer support for sub-retrievers**: The ability to use a top-level normalizer as a default for sub-retrievers was introduced in Elasticsearch 9.2+. In earlier versions, only per-retriever normalizers are supported.
-    :::
+    {applies_to}`stack: ga 9.2`
 
     ::::{warning}
     Avoid using `none` as that will disable normalization and may bias the result set towards lexical matches.
@@ -83,8 +80,7 @@ Each entry in the `retrievers` array specifies the following parameters:
 
     Specifies how the retriever's score will be normalized before applying the specified `weight`.
     See [normalizers](#linear-retriever-normalizers) for supported values.
-    If not specified, uses the top-level `normalizer` or defaults to `none` if no top-level normalizer is set.
-    {applies_to}`stack: ga 9.2`
+    If not specified, uses the top-level `normalizer` (9.2+) or defaults to `none` (earlier versions).
 
 See also [this hybrid search example](retrievers-examples.md#retrievers-examples-linear-retriever) using a linear retriever on how to independently configure and apply normalizers to retrievers.