fix: Improve clarity around customizations' supported languages

Author: BriannaDelgado

api-reference/document.mdx

@@ -34,7 +34,7 @@ Because the request includes a file upload, it must be an HTTP POST request with
 
 Please be aware that the uploaded document is automatically removed from the server once the translated document has been downloaded. You have to upload the document again in order to restart the translation.
 
-You may specify the glossary to use for the document translation using the `glossary_id` parameter. **Important:** This requires the `source_lang` parameter to be set and the language pair of the glossary has to match the language pair of the request.
+You may specify the glossary to use for the document translation using the `glossary_id` parameter. **Important:** This requires the `source_lang` parameter to be set and the language pair of the glossary has to match the language pair of the request. If the target language is a variant (e.g., `EN-GB`), a glossary with the base language (e.g., `EN`) as its target language will still be applied.
 
 For more detail about request body parameters, see the [Request Body Descriptions](/api-reference/document#request-body-descriptions) section further down on the page.
 
@@ -156,7 +156,10 @@ These examples are for demonstration purposes only. In production code, the auth
   </ul>
 </ParamField>
 <ParamField body="glossary_id" type="string">
-  A unique ID assigned to a glossary.  
+  Specify the glossary to use for the document translation.
+  <Note>
+    <strong>Important:</strong> This requires the <code>source_lang</code> parameter to be set and the language pair of the glossary has to match the language pair of the request. If the target language is a variant (e.g., <code>EN-GB</code>), a glossary with the base language (e.g., <code>EN</code>) as its target language will still be applied.
+  </Note>
 </ParamField>
 <ParamField body="output_format" type="string">
   File extension of desired format of translated file, for example: `pdf`. If unspecified, by default the translated file will be in the same format as the input file.

api-reference/openapi.yaml

@@ -433,15 +433,15 @@ paths:
                   description: |-
                     Specify the glossary to use for the translation. **Important:** This requires the `source_lang`
                     parameter to be set. The language pair of the glossary has to match the language pair of the
-                    request.
+                    request. If the target language is a variant (e.g., `EN-GB`), a glossary with the base language (e.g., `EN`) as its target language will still be applied.
                   type: string
                   example: def3a26b-3e84-45b3-84ae-0c0aaf3525f7
                 style_id:
                   description: |-
-                    Specify the [style rule list](/api-reference/style-rules) to use for the translation. 
+                    Specify the [style rule list](/api-reference/style-rules) to use for the translation.
+
+                    **Important:**  The target language has to match the language of the style rule list. If the target language is a variant (e.g., `EN-GB`), a style rule list created for the base language (e.g., `EN`) will still be applied.
 
-                    **Important:**  The target language has to match the language of the style rule list. 
-                    
                     **Note:** Any request with the `style_id` parameter enabled will use `quality_optimized` models. Requests combining `style_id` and `model_type: latency_optimized` will be rejected.
                   type: string
                   example: 7ff9bfd6-cd85-4190-8503-d6215a321519
@@ -525,7 +525,7 @@ paths:
                   description: |-
                     Specify the glossary to use for the translation. **Important:** This requires the `source_lang`
                     parameter to be set. The language pair of the glossary has to match the language pair of the
-                    request.
+                    request. If the target language is a variant (e.g., `EN-GB`), a glossary with the base language (e.g., `EN`) as its target language will still be applied.
                   type: string
                   example: def3a26b-3e84-45b3-84ae-0c0aaf3525f7
                 translation_memory_id:
@@ -682,7 +682,12 @@ paths:
                 formality:
                   $ref: '#/components/schemas/Formality'
                 glossary_id:
-                  $ref: '#/components/schemas/GlossaryId'
+                  description: |-
+                    Specify the glossary to use for the document translation. **Important:** This requires the `source_lang`
+                    parameter to be set. The language pair of the glossary has to match the language pair of the
+                    request. If the target language is a variant (e.g., `EN-GB`), a glossary with the base language (e.g., `EN`) as its target language will still be applied.
+                  type: string
+                  example: def3a26b-3e84-45b3-84ae-0c0aaf3525f7
                 enable_beta_languages:
                   description: |-
                     No languages are currently in Beta. This parameter is maintained for backward compatibility and has no effect. Previously enabled 81 languages that are now part of the standard language list. See the [full list](/docs/getting-started/supported-languages).

api-reference/translate.mdx

@@ -284,13 +284,13 @@ error.
 <ParamField body="glossary_id" type="string">
   Specify the glossary to use for the translation.
   <Note>
-    <strong>Important:</strong> This requires the <code>source_lang</code> parameter to be set and the language pair of the glossary has to match the language pair of the request.
+    <strong>Important:</strong> This requires the <code>source_lang</code> parameter to be set and the language pair of the glossary has to match the language pair of the request. If the target language is a variant (e.g., <code>EN-GB</code>), a glossary with the base language (e.g., <code>EN</code>) as its target language will still be applied.
   </Note>
 </ParamField>
 <ParamField body="style_id" type="string">
   Specify the style rule list to use for the translation which can be used to customize translations according to the selected formatting and style conventions.
   <Info>
-    The target language has to match the language of the style rule list. 
+    The target language has to match the language of the style rule list. If the target language is a variant (e.g., `EN-GB`), a style rule list created for the base language (e.g., `EN`) will still be applied.
 
     Additionally, any request with the `style_id` parameter enabled will default to use the `quality_optimized` model type. Requests combining `style_id` and `model_type: latency_optimized` will be rejected.
   </Info>

docs/getting-started/supported-languages.mdx

@@ -17,7 +17,3 @@ import { LanguageTable } from "/snippets/language-table.jsx"
 <Info>
   Text improvement languages have not yet been added to the [`/languages` endpoint](/api-reference/languages/retrieve-supported-languages). For `/write/rephrase`, `writing_style` and `tone` currently work in `DE`, `EN-GB`, and `EN-US`.
 </Info>
-
-<Info>
-  Style rules are supported for the following target languages: `de`, `en`, `es`, `fr`, `it`, `ja`, `ko`, and `zh`. For more details, see the [Style Rules API documentation](/api-reference/style-rules).
-</Info>