diff --git a/specs/common/schemas/IndexSettings.yml b/specs/common/schemas/IndexSettings.yml
index b89375ebcdc..898a0f9c89a 100644
--- a/specs/common/schemas/IndexSettings.yml
+++ b/specs/common/schemas/IndexSettings.yml
@@ -618,16 +618,22 @@ indexSettingsAsSearchParams:
       items:
         $ref: '#/alternativesAsExact'
       description: |
-        Alternatives of query words that should be considered as exact matches by the Exact ranking criterion.
+        Determine which plurals and synonyms should be considered an exact matches.
+
+        By default, Algolia treats singular and plural forms of a word, and single-word synonyms, as [exact](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#exact) matches when searching.
+        For example:
+
+        - "swimsuit" and "swimsuits" are treated the same
+        - "swimsuit" and "swimwear" are treated the same (if they are [synonyms](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/#regular-synonyms)).
 
         - `ignorePlurals`.
           Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.
 
         - `singleWordSynonym`.
-          Single-word synonyms, such as "NY/NYC" are considered exact matches.
+          Single-word synonyms, such as "NY" = "NYC", are considered exact matches.
 
         - `multiWordsSynonym`.
-          Multi-word synonyms, such as "NY/New York" are considered exact matches.
+          Multi-word synonyms, such as "NY" = "New York", are considered exact matches.
       default: [ignorePlurals, singleWordSynonym]
       x-categories:
         - Query strategy