Correct collation Analyzer breaking change

Author: Simran-B

site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md

@@ -174,19 +174,22 @@ instead in most cases, and in some cases AQL can be sufficient.
 
 The [`collation` Analyzer](../../index-and-search/analyzers.md#collation) lets
 you adhere to the alphabetic order of a language in range queries. For example,
-using the Swedish locale (`sv`), `å` goes after `z` and not near `a`, which
-can impact queries.
-
-Sorting by the output of the `collation` Analyzer like
-`SORT TOKENS(<text>, <collationAnalyzer>` did not produce meaningful results in
-previous versions. Sorting the letters `å`, `a`, `b`, `z` resulted in the order
-`b` `a` `å` `z` using an English locale (`en`) and `b` `å` `a` `z` using a
-Swedish locale (`sv`).
-
-In v3.12, this now sorts properly to `a` `å` `b` `z` (English) and
-`a` `b` `z` `å` (Swedish). This change can make queries behave differently
-compared to v3.11 and older, and inverted indexes and Views using
-`collation` Analyzers need to be recreated to ensure that they work correctly.
+using a Swedish locale (`sv`), the sorting order is `å` after `z`, whereas using
+an English locale (`en`), `å` is preceded by `a`. This impacts queries with
+`SEARCH` expressions like `doc.text < "c"`, excluding `å` when using the Swedish
+locale.
+
+ArangoDB 3.12 bundles an upgraded version of the ICU library. It is used for
+Unicode character handling including text sorting. Because of changes in ICU,
+data produced by the `collation` Analyzer in previous versions is not compatible
+with ArangoDB v3.12. You need to **recreate inverted indexes and Views that use
+`collation` Analyzers** to ensure that they work correctly. Otherwise,
+range queries involving the `collation` Analyzers and indexes created in v3.11
+or older versions may behave in unpredicted ways.
+
+Note that sorting by the output of the `collation` Analyzer like
+`SORT TOKENS(<text>, <collationAnalyzer>` is still not a supported feature and
+doesn't produce meaningful results.
 
 ## Control character escaping in audit log
 

site/content/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md

@@ -174,19 +174,22 @@ instead in most cases, and in some cases AQL can be sufficient.
 
 The [`collation` Analyzer](../../index-and-search/analyzers.md#collation) lets
 you adhere to the alphabetic order of a language in range queries. For example,
-using the Swedish locale (`sv`), `å` goes after `z` and not near `a`, which
-can impact queries.
-
-Sorting by the output of the `collation` Analyzer like
-`SORT TOKENS(<text>, <collationAnalyzer>` did not produce meaningful results in
-previous versions. Sorting the letters `å`, `a`, `b`, `z` resulted in the order
-`b` `a` `å` `z` using an English locale (`en`) and `b` `å` `a` `z` using a
-Swedish locale (`sv`).
-
-In v3.12, this now sorts properly to `a` `å` `b` `z` (English) and
-`a` `b` `z` `å` (Swedish). This change can make queries behave differently
-compared to v3.11 and older, and inverted indexes and Views using
-`collation` Analyzers need to be recreated to ensure that they work correctly.
+using a Swedish locale (`sv`), the sorting order is `å` after `z`, whereas using
+an English locale (`en`), `å` is preceded by `a`. This impacts queries with
+`SEARCH` expressions like `doc.text < "c"`, excluding `å` when using the Swedish
+locale.
+
+ArangoDB 3.12 bundles an upgraded version of the ICU library. It is used for
+Unicode character handling including text sorting. Because of changes in ICU,
+data produced by the `collation` Analyzer in previous versions is not compatible
+with ArangoDB v3.12. You need to **recreate inverted indexes and Views that use
+`collation` Analyzers** to ensure that they work correctly. Otherwise,
+range queries involving the `collation` Analyzers and indexes created in v3.11
+or older versions may behave in unpredicted ways.
+
+Note that sorting by the output of the `collation` Analyzer like
+`SORT TOKENS(<text>, <collationAnalyzer>` is still not a supported feature and
+doesn't produce meaningful results.
 
 ## Control character escaping in audit log