post-review correction

Author: JPryce-Aklundh

modules/ROOT/pages/indexes/search-performance-indexes/managing-indexes.adoc

@@ -290,12 +290,12 @@ Text indexes are only used for exact query matches. To perform approximate match
 ==== Trigram indexing
 
 The default text index provider, `text-2.0`, uses trigram indexing.
-This means that `STRING` values are indexed into overlapping trigrams, each containing three characters.
+This means that `STRING` values are indexed into overlapping trigrams, each containing three Unicode code points.
 For example, the word `"developer"` would be indexed by the following trigrams: `["dev", "eve", "vel", "elo", "lop", "ope", "per"]`.
 
-This makes text indexes particularly suited for substring (`CONTAINS`) and suffix (`ENDS WITH`) searches.
+This makes text indexes particularly suitable for substring (`CONTAINS`) and suffix (`ENDS WITH`) searches, as well as prefix searches (`STARTS WITH`).
 For example, searches like `CONTAINS "vel"` or `ENDS WITH "per"` can be efficiently performed by directly looking up the relevant trigrams in the index.
-By comparison, range indexes, which indexes `STRING` values alphabetically (see xref:indexes/search-performance-indexes/using-indexes.adoc#range-index-backed-order-by[Range index-backed `ORDER BY`] for more information) and are therefore more suited for prefix searches (`STARTS WITH`), would need to scan through all indexed values to check if `"vel"` existed anywhere within the text.
+By comparison, range indexes, which indexes `STRING` values lexicographically (see xref:indexes/search-performance-indexes/using-indexes.adoc#range-index-backed-order-by[Range index-backed `ORDER BY`] for more information) and are therefore more suited for prefix searches, would need to scan through all indexed values to check if `"vel"` existed anywhere within the text.
 For more information, see xref:indexes/search-performance-indexes/using-indexes.adoc#text-indexes[The impact of indexes on query performance -> Text indexes].
 
 [discrete]