Fix typo in themes.mdx

api-playground/overview.mdx

@@ -15,7 +15,7 @@
 
 The playground is automatically generated from your OpenAPI specification or AsyncAPI schema so any updates to your API are automatically reflected in the playground. You can also manually create API reference pages after defining a base URL and authentication method in your `docs.json`.
 
 We recommend generating your API playground from an OpenAPI specification. See [OpenAPI Setup](/api-playground/openapi-setup) for more information on creating your OpenAPI document.
 
 ## Getting started
 
@@ -50,7 +50,7 @@
 
     To generate pages for only specific endpoints, list the endpoints in the `pages` property of the navigation element.
 
-    This example generates pages for only the `GET /users` and `POST /users` endpoints. To genereate other endpoint pages, add additional endpoints to the `pages` array.
+    This example generates pages for only the `GET /users` and `POST /users` endpoints. To generate other endpoint pages, add additional endpoints to the `pages` array.
 
     ```json
     "navigation": {
@@ -79,7 +79,7 @@
     <Expandable title="playground" defaultOpen="True">
     <ResponseField name="display" type="&quot;interactive&quot; | &quot;simple&quot; | &quot;none&quot;">
         The display mode of the API playground.
         - `"interactive"`: Display the interactive playground.
         - `"simple"`: Display a copyable endpoint with no playground.
         - `"none"`: Display nothing.
 
@@ -109,19 +109,19 @@
 
 ```json
 {
  "api": {
    "playground": {
      "display": "interactive"
    },
    "examples": {
      "languages": ["curl", "python", "javascript"],
      "defaults": "required"
    }
  }
 }
 ```
 
 This example configures the API playground to be interactive with example code snippets for cURL, Python, and JavaScript. Only required parameters are shown in the code snippets.
 
 ### Custom endpoint pages
 
@@ -133,9 +133,9 @@
 - Add additional content like examples
 - Control playground behavior per page
 
 The `x-mint` extension is recommended so that all of your API documentation is automatically generated from your OpenAPI specification and maintained in one file.
 
 Individual `MDX` pages are recommended for small APIs or when you want to experiment with changes on a per-page basis.
 
 For more information, see [x-mint extension](/api-playground/openapi-setup#x-mint-extension) and [MDX Setup](/api-playground/mdx/configuration).
 

themes.mdx

@@ -28,13 +28,13 @@
         </div>
       </div>
     </a>
   );
 };
 
 <div className="pt-10 pb-24 px-4 px-4 max-w-3xl mx-auto prose prose-gray">
   <label className="eyebrow h-5 text-primary dark:text-primary-light text-sm font-semibold">Core Concepts</label>
   <h1 className="mt-1 mb-2 text-2xl sm:text-3xl text-gray-900 tracking-tight dark:text-gray-200 font-semibold">Themes</h1>
-  <label className="text-lg prose prose-gray dark:prose-invert">Custom the appearance of your documentation<br /><br />Configure [theme](settings#param-theme) in docs.json using one of the following themes.</label>
+  <label className="text-lg prose prose-gray dark:prose-invert">Customize the appearance of your documentation<br /><br />Configure [theme](settings#param-theme) in docs.json using one of the following themes.</label>
 
 <br />