Fixed localization page

Author: ruhanponnada

settings/versioning.mdx

@@ -1,4 +1,4 @@
- ---
+---
 title: "Versioning & Localization"
 description: "Build separate versions or localizations"
 icon: "square-chevron-down"
@@ -12,16 +12,20 @@ These guides will assume `v1` pages are in a folder named `v1`, `v2` pages are i
 
 ### Setup
 
-Add `"versions": ["v2", "v1"]` to your `mint.json` file where `v1` and `v2` are the names of your versions. You can put any number of versions in this array. The first version from the array serves as the default version.
+Add `"versions": ["v2", "v1"]` to your `docs.json` file where `v1` and `v2` are the names of your versions. You can put any number of versions in this array. The first version from the array serves as the default version.
 
 If you would like to specify a default version, you can do so like this:
 ```json
 "global": {
   "versions": [
     {
-      "version": "version-name",
+      "version": "v1",
       "default": true,
-      "href": "link-to-version"
+      "href": "pathname-to-v1"
+    },
+    {
+      "version": "v2",
+      "href": "pathname-to-v2"
     }
   ]
 }
@@ -172,7 +176,7 @@ Common errors and how to fix them
 
 ### Setup
 
-`"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.
+`"languages"` in your `docs.json` can be leveraged to create different language versions by adding a `language` value to the version. The first language from the array serves as the default language.
 
 We currently support localization in English (`en`), Chinese (`cn`), Spanish (`es`), French (`fr`), Japanese (`jp`), Portuguese (`pt`), Portuguese (Brazil) (`pt-BR`), and German (`de`).
 
@@ -196,7 +200,7 @@ We currently support localization in English (`en`), Chinese (`cn`), Spanish (`e
 ```
 
 <Tip>
-  The languages dropdown will show your localizations in the order you include
+  The languages dropdown will show your languages in the order you include
   them in the `docs.json`.
 </Tip>