update copy

Author: hahnbeelee

settings/global.mdx

@@ -308,8 +308,8 @@ locale. We currently support localization in English, Chinese, Spanish, French,
 Japanese, and Portuguese.
 
 <Info>
-  Localization applies to the UI and fixed assets in the docs, such as "was this
-  page helpful".
+  Localization auto-translates the UI and fixed assets in the docs, such as "Was
+  this page helpful?". You must translate the content of the pages yourself.
 </Info>
 
 For more information, please refer to our

settings/versioning.mdx

@@ -1,7 +1,7 @@
 ---
-title: 'Versioning & Localization'
-description: 'Build separate versions or localizations'
-icon: 'square-chevron-down'
+title: "Versioning & Localization"
+description: "Build separate versions or localizations"
+icon: "square-chevron-down"
 ---
 
 Mintlify supports versioning or localization. You can use one or the other, not both.
@@ -49,14 +49,17 @@ You can also specify the version of a single page in the page metadata. Versions
 
 ```yaml Pages (quickstart.mdx)
 ---
-title: 'Quickstart'
-version: 'v2'
+title: "Quickstart"
+version: "v2"
 ---
 ```
+
 </CodeGroup>
 
 <Warning>
-  While it is possible to nest versioned groups within versioned groups, it is not recommended. If you do take this approach, the more deeply-nested version takes precedence.
+  While it is possible to nest versioned groups within versioned groups, it is
+  not recommended. If you do take this approach, the more deeply-nested version
+  takes precedence.
 </Warning>
 
 #### Versioning Tabs and Anchors
@@ -104,14 +107,18 @@ In `mint.json`, simply add `version` to your tab or anchor. Tabs and anchors wit
   },
 ],
 ```
+
 </CodeGroup>
 
 #### Sharing Between Versions
 
 Not _all_ content has to be hidden though! Any content without a specified version appears in every version so you don't have to duplicate content!
 
 <Tip>
-  When using localization with versioning, each version can have its own set of translations. This means you can have different language versions for different API versions, giving you full flexibility in managing both versioned and localized content.
+  When using localization with versioning, each version can have its own set of
+  translations. This means you can have different language versions for
+  different API versions, giving you full flexibility in managing both versioned
+  and localized content.
 </Tip>
 
 ### Troubleshooting
@@ -123,6 +130,7 @@ Common errors and how to fix them
     You likely nested a version inside of another. For example, your group had version "v1" but your page had version "v2".
 
     We do not recommend nesting versions inside of each other because it's hard to maintain your docs later.
+
   </Accordion>
 
   <Accordion title="Missing Pages" icon="circle-exclamation">
@@ -136,13 +144,11 @@ Common errors and how to fix them
 
 ### Setup
 
-`"versions"` in your `mint.json` can be leveraged to create different language versions. The first localization from the array serves as the default localization.
+`"versions"` in your `mint.json` can be leveraged to create different language versions by adding a `locale` value to the version. The first localization from the array serves as the default localization.
 
-We currently support localization in English (`en`), Chinese, Spanish (`es`), French (`fr`), Japanese, and Portuguese.
+We currently support localization in English (`en`), Chinese (`cn`), Spanish (`es`), French (`fr`), Japanese (`jp`), Portuguese (`pt`), and German (`de`).
 
-Set your localization in your `mint.json` file like this:
-
-```json
+```json mint.json example
 "versions": [
   {
     "name": "English",
@@ -160,8 +166,8 @@ Set your localization in your `mint.json` file like this:
 ```
 
 <Tip>
-  The versions dropdown will show your localizations in the order you include them in
-  `mint.json`.
+  The versions dropdown will show your localizations in the order you include
+  them in `mint.json`.
 </Tip>
 
-Once setup, the rest of localization is handled by the versioning setup described above.
+Once setup, the rest of localization is handled by the versioning setup described above.