Fix typos in previous release notes and sources

Author: charlotte-hoblik

docs/release-notes/changelog-bundles/9.1.0.yml

@@ -669,6 +669,11 @@ changelogs:
     area: Machine Learning
     type: enhancement
     issues: []
+  - pr: 2831
+    summary: Track memory used in the hierarchical results normalizer
+    area: Machine Learning
+    type: enhancement
+    issues: []
   - pr: 125520
     summary: Add `FailedShardEntry` info to shard-failed task source string
     area: Allocation
@@ -1060,7 +1065,7 @@ changelogs:
       notable: true
       title: Upgrade `repository-s3` to AWS SDK v2
       body: |-
-        In earlier versions of {es} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {es} {minor-version} so we have migrated this plugin to the newer AWS SDK v2.
+        In earlier versions of {{es}} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {{es}} 9.1 so we have migrated this plugin to the newer AWS SDK v2.
         The two SDKs are not quite compatible, so please check the breaking changes documentation and test the new version thoroughly before upgrading any production workloads.
       pr: 126843
   - pr: 126856
@@ -1119,8 +1124,7 @@ changelogs:
         new data streams by specifying it in the new `data_stream_options` field
         inside of a component or index template:
 
-        [source,yaml]
-        ----
+        ```yaml
         PUT _index_template/my-template
         {
           "index_patterns": ["logs-test-*"],
@@ -1133,20 +1137,19 @@ changelogs:
             }
           }
         }'
-        ----
+        ```
 
         Existing data streams can be configured with the new data stream
         `_options` endpoint:
 
-        [source,yaml]
-        ----
+        ```yaml
         PUT _data_stream/logs-test-apache/_options
         {
           "failure_store": {
             "enabled": "true"
           }
         }
-        ----
+        ```
 
         When redirection is enabled, any ingestion related failures will be
         captured in the failure store if the cluster is able to, along with the
@@ -1158,26 +1161,24 @@ changelogs:
         stream data. In order to retrieve the failures, we use the `_search` API
         along with a new bit of index pattern syntax, the `::` selector.
 
-        [source,yaml]
-        ----
+        ```yaml
         POST logs-test-apache::failures/_search
-        ----
+        ```
 
         This index syntax informs the search operation to target the indices in
         its failure store instead of its backing indices. It can be mixed in a
         number of ways with other index patterns to include their failure store
         indices in the search operation:
 
-        [source,yaml]
-        ----
+        ```yaml
         POST logs-*::failures/_search
         POST logs-*,logs-*::failures/_search
         POST *::failures/_search
         POST _query
         {
           "query": "FROM my_data_stream*::failures"
         }
-        ----
+        ```
       pr: 126973
   - pr: 127006
     summary: Correctly handle non-integers in nested paths in the remove processor
@@ -1887,24 +1888,22 @@ changelogs:
 
         Example:
 
-        [source,yaml]
-        ----------------------------
+        ```yaml
         FROM test
         | FORK
         ( WHERE content:"fox" )
         ( WHERE content:"dog" )
         | SORT _fork
-        ----------------------------
+        ```
 
         The FORK command add a discriminator column called `_fork`:
 
-        [source,yaml]
-        ----------------------------
+        ```yaml
         | id  | content   | _fork |
         |-----|-----------|-------|
         | 3   | brown fox | fork1 |
         | 4   | white dog | fork2 |
-        ----------------------------
+        ```
       pr: 129606
   - pr: 129647
     summary: Fix `PushQueriesIT.testLike()` fails

docs/release-notes/index.md

@@ -127,7 +127,7 @@ This caused unintended timeouts or cancellations during subsequent phases under
 ### Highlights [elasticsearch-9.1.0-highlights]
 
 ::::{dropdown} Upgrade `repository-s3` to AWS SDK v2
-In earlier versions of {es} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {es} {minor-version} so we have migrated this plugin to the newer AWS SDK v2.
+In earlier versions of {{es}} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {{es}} 9.1 so we have migrated this plugin to the newer AWS SDK v2.
 The two SDKs are not quite compatible, so please check the breaking changes documentation and test the new version thoroughly before upgrading any production workloads.
 ::::
 
@@ -153,8 +153,7 @@ Users can enable redirection of ingest failures to the failure store on
 new data streams by specifying it in the new `data_stream_options` field
 inside of a component or index template:
 
-[source,yaml]
-----
+```yaml
 PUT _index_template/my-template
 {
   "index_patterns": ["logs-test-*"],
@@ -167,20 +166,19 @@ PUT _index_template/my-template
     }
   }
 }'
-----
+```
 
 Existing data streams can be configured with the new data stream
 `_options` endpoint:
 
-[source,yaml]
-----
+```yaml
 PUT _data_stream/logs-test-apache/_options
 {
   "failure_store": {
     "enabled": "true"
   }
 }
-----
+```
 
 When redirection is enabled, any ingestion related failures will be
 captured in the failure store if the cluster is able to, along with the
@@ -192,26 +190,24 @@ default as they are stored in different indices than the normal data
 stream data. In order to retrieve the failures, we use the `_search` API
 along with a new bit of index pattern syntax, the `::` selector.
 
-[source,yaml]
-----
+```yaml
 POST logs-test-apache::failures/_search
-----
+```
 
 This index syntax informs the search operation to target the indices in
 its failure store instead of its backing indices. It can be mixed in a
 number of ways with other index patterns to include their failure store
 indices in the search operation:
 
-[source,yaml]
-----
+```yaml
 POST logs-*::failures/_search
 POST logs-*,logs-*::failures/_search
 POST *::failures/_search
 POST _query
 {
   "query": "FROM my_data_stream*::failures"
 }
-----
+```
 ::::
 
 ::::{dropdown} Mark Token Pruning for Sparse Vector as GA
@@ -234,24 +230,22 @@ Conceptually, fork is:
 
 Example:
 
-[source,yaml]
-----------------------------
+```yaml
 FROM test
 | FORK
 ( WHERE content:"fox" )
 ( WHERE content:"dog" )
 | SORT _fork
-----------------------------
+```
 
 The FORK command add a discriminator column called `_fork`:
 
-[source,yaml]
-----------------------------
+```yaml
 | id  | content   | _fork |
 |-----|-----------|-------|
 | 3   | brown fox | fork1 |
 | 4   | white dog | fork2 |
-----------------------------
+```
 ::::
 
 ::::{dropdown} ES|QL cross-cluster querying is now generally available
@@ -468,6 +462,7 @@ Machine Learning:
 * Mark token pruning for sparse vector as GA [#128854](https://github.com/elastic/elasticsearch/pull/128854)
 * Move to the Cohere V2 API for new inference endpoints [#129884](https://github.com/elastic/elasticsearch/pull/129884)
 * Semantic Text Chunking Indexing Pressure [#125517](https://github.com/elastic/elasticsearch/pull/125517)
+* Track memory used in the hierarchical results normalizer [#2831](https://github.com/elastic/ml-cpp/pull/2831)
 * Upgrade AWS v2 SDK to 2.30.38 [#124738](https://github.com/elastic/elasticsearch/pull/124738)
 * [Inference API] Propagate product use case http header to EIS [#124025](https://github.com/elastic/elasticsearch/pull/124025)
 * [ML] Add HuggingFace Chat Completion support to the Inference Plugin [#127254](https://github.com/elastic/elasticsearch/pull/127254)