diff --git a/.code-samples.meilisearch.yaml b/.code-samples.meilisearch.yaml
index 8d4fe3615..975296ad7 100644
--- a/.code-samples.meilisearch.yaml
+++ b/.code-samples.meilisearch.yaml
@@ -1373,7 +1373,7 @@ search_parameter_reference_locales_1: |-
-X POST 'http://localhost:7700/indexes/INDEX_NAME/search' \
-H 'Content-Type: application/json' \
--data-binary '{
- "q": "進撃の巨人",
+ "q": "QUERY TEXT IN JAPANESE",
"locales": ["jpn"]
}'
get_localized_attribute_settings_1: |-
diff --git a/reference/api/search.mdx b/reference/api/search.mdx
index 464487421..0de79b11d 100644
--- a/reference/api/search.mdx
+++ b/reference/api/search.mdx
@@ -1254,7 +1254,7 @@ Return document embedding data with search results. If `true`, Meilisearch will
### Query locales
**Parameter**: `locales`
-**Expected value**: array of [supported ISO-639-2B locales](/reference/api/settings#localized-attributes-object)
+**Expected value**: array of [supported ISO-639 locales](/reference/api/settings#localized-attributes-object)
**Default value**: `[]`
By default, Meilisearch auto-detects the language of a query. Use this parameter to explicitly state the language of a query.
@@ -1281,7 +1281,6 @@ For full control over the way Meilisearch detects languages during indexing and
{
"id": 0,
"title": "DOCUMENT NAME",
- "overview_cn": "OVERVIEW TEXT IN CHINESE",
"overview_jp": "OVERVIEW TEXT IN JAPANESE"
}
…
diff --git a/reference/api/settings.mdx b/reference/api/settings.mdx
index 427dedf15..4b73d6221 100644
--- a/reference/api/settings.mdx
+++ b/reference/api/settings.mdx
@@ -815,7 +815,9 @@ Locale objects must have the following fields:
#### `locales`
-Meilisearch supports the following `locales`: `epo`, `eng`, `rus`, `cmn`, `spa`, `por`, `ita`, `ben`, `fra`, `deu`, `ukr`, `kat`, `ara`, `hin`, `jpn`, `heb`, `yid`, `pol`, `amh`, `jav`, `kor`, `nob`, `dan`, `swe`, `fin`, `tur`, `nld`, `hun`, `ces`, `ell`, `bul`, `bel`, `mar`, `kan`, `ron`, `slv`, `hrv`, `srp`, `mkd`, `lit`, `lav`, `est`, `tam`, `vie`, `urd`, `tha`, `guj`, `uzb`, `pan`, `aze`, `ind`, `tel`, `pes`, `mal`, `ori`, `mya`, `nep`, `sin`, `khm`, `tuk`, `aka`, `zul`, `sna`, `afr`, `lat`, `slk`, `cat`, `tgl`, `hye`.
+Meilisearch supports the following [ISO-639-3](https://iso639-3.sil.org/) three-letter `locales`: `epo`, `eng`, `rus`, `cmn`, `spa`, `por`, `ita`, `ben`, `fra`, `deu`, `ukr`, `kat`, `ara`, `hin`, `jpn`, `heb`, `yid`, `pol`, `amh`, `jav`, `kor`, `nob`, `dan`, `swe`, `fin`, `tur`, `nld`, `hun`, `ces`, `ell`, `bul`, `bel`, `mar`, `kan`, `ron`, `slv`, `hrv`, `srp`, `mkd`, `lit`, `lav`, `est`, `tam`, `vie`, `urd`, `tha`, `guj`, `uzb`, `pan`, `aze`, `ind`, `tel`, `pes`, `mal`, `ori`, `mya`, `nep`, `sin`, `khm`, `tuk`, `aka`, `zul`, `sna`, `afr`, `lat`, `slk`, `cat`, `tgl`, `hye`.
+
+You may alternatively use [ISO-639-1 two-letter equivalents](https://iso639-3.sil.org/code_tables/639/data) to the supported `locales`.
You may also assign an empty array to `locales`. In this case, Meilisearch will auto-detect the language of the associated `attributePatterns`.