Add proper language support for syntax highlighting to all code blocks (#807)

* Add proper language support for syntax highlighting to all code blocks

* Camel case inline code

Author: ricardonunez-io

api-playground/customization/adding-sdk-examples.mdx

@@ -25,7 +25,7 @@ Here is an example of code samples for a plant tracking app, which has both a Ba
 paths:
   /plants:
     get:
-      ...
+      # ...
       x-codeSamples:
         - lang: bash
           label: List all unwatered plants

api-playground/customization/complex-data-types.mdx

@@ -32,7 +32,7 @@ org_with_users:
         users:
           type: array
           description: An array containing all users in the organization
-...
+# ...
 components:
   schemas:
     Org:
@@ -67,14 +67,14 @@ delivery_address:
         address_line_1:
           type: string
           description: The street address of the recipient
-        ...
+        # ...
     - title: POBox
       type: object
       properties:
         box_number:
           type: string
           description: The number of the PO Box
-        ...
+        # ...
 ```
 
 <ParamField body="delivery_address" type="object">

api-playground/customization/managing-page-visibility.mdx

@@ -39,24 +39,24 @@ Here are examples of how to use each property in an OpenAPI schema document for
   "/plants": {
     "get": {
       "description": "Returns all plants from the store",
-      "parameters": { ... },
-      "responses": { ... }
+      "parameters": { /*...*/ },
+      "responses": { /*...*/ }
     }
   },
   "/hidden_plants": {
     "get": {
       "x-hidden": true,
       "description": "Returns all somewhat secret plants from the store",
-      "parameters": { ... },
-      "responses": { ... }
+      "parameters": { /*...*/ },
+      "responses": { /*...*/ }
     }
   },
   "/secret_plants": {
     "get": {
       "x-excluded": true,
       "description": "Returns all top secret plants from the store (do not publish this endpoint!)",
-      "parameters": { ... },
-      "responses": { ... }
+      "parameters": { /*...*/ },
+      "responses": { /*...*/ }
     }
   }
 },

api-playground/customization/multiple-responses.mdx

@@ -28,4 +28,4 @@ responses:
               countryCode: "GB"
               currencyCode: "GBP"
               taxRate: 0.20
-```
+```

api-playground/mdx/authentication.mdx

@@ -23,7 +23,7 @@ A page's authentication method will override a global method if both are set.
 }
 ```
 
-```md Page Metadata
+```mdx Page Metadata
 ---
 title: "Your page title"
 authMethod: "bearer"
@@ -46,7 +46,7 @@ authMethod: "bearer"
 }
 ```
 
-```md Page Metadata
+```mdx Page Metadata
 ---
 title: "Your page title"
 authMethod: "basic"
@@ -70,7 +70,7 @@ authMethod: "basic"
 }
 ```
 
-```md Page Metadata
+```mdx Page Metadata
 ---
 title: "Your page title"
 authMethod: "key"
@@ -84,7 +84,7 @@ authMethod: "key"
 The "none" authentication method is useful to disable authentication on a specific endpoint after setting a default in docs.json.
 
 <CodeGroup>
-```md Page Metadata
+```mdx Page Metadata
 ---
 title: "Your page title"
 authMethod: "none"

api-playground/mdx/configuration.mdx

@@ -40,7 +40,7 @@ To generate pages for API endpoints using `MDX`, configure your API settings in
 
     Each API endpoint page should have a corresponding `MDX` file. At the top of each file, define `title` and `api`:
 
-    ```md
+    ```mdx
     ---
     title: 'Create new user'
     api: 'POST https://api.mintlify.com/user'
@@ -61,11 +61,12 @@ To generate pages for API endpoints using `MDX`, configure your API settings in
 
     You can override the globally-defined display mode for the API playground per page by adding `playground` at the top of the `MDX` file:
 
-    ```md
+    ```mdx
     ---
     title: 'Create new user'
     api: 'POST https://api.mintlify.com/user'
     playground: 'none'
+    ---
     ```
 
   </Step>
@@ -95,7 +96,7 @@ A page's authentication method will override a global method if both are set.
 }
 ```
 
-```md Page Metadata
+```mdx Page Metadata
 ---
 title: "Your page title"
 authMethod: "bearer"
@@ -118,7 +119,7 @@ authMethod: "bearer"
 }
 ```
 
-```md Page Metadata
+```mdx Page Metadata
 ---
 title: "Your page title"
 authMethod: "basic"
@@ -142,7 +143,7 @@ authMethod: "basic"
 }
 ```
 
-```md Page Metadata
+```mdx Page Metadata
 ---
 title: "Your page title"
 authMethod: "key"
@@ -156,7 +157,7 @@ authMethod: "key"
 The `none` authentication method is useful to disable authentication on a specific endpoint after setting a default in docs.json.
 
 <CodeGroup>
-```md Page Metadata
+```mdx Page Metadata
 ---
 title: "Your page title"
 authMethod: "none"

api-playground/openapi-setup.mdx

@@ -162,7 +162,7 @@ If you want to reference an external OpenAPI file, add the file's URL to your `d
 
 <CodeGroup>
 
-```md Example
+```mdx Example
 ---
 title: "Get users"
 description: "Returns all plants from the system that the user has access to"
@@ -172,7 +172,7 @@ version: "1.0"
 ---
 ```
 
-```md Format
+```mdx Format
 ---
 title: "title of the page"
 description: "description of the page"
@@ -225,14 +225,14 @@ You can create individual pages for any OpenAPI schema defined in an OpenAPI doc
 
 <CodeGroup>
 
-```md Example
+```mdx Example
 ---
 openapi-schema: OrderItem
 ---
 ```
 
 
-```md Format
+```mdx Format
 ---
 openapi-schema: "schema-key"
 ---

api-playground/overview.mdx

@@ -25,7 +25,7 @@ We recommend generating your API playground from an OpenAPI specification. See [
     Make sure that your OpenAPI specification file is valid using the [Swagger Editor](https://editor.swagger.io/) or [Mint CLI](https://www.npmjs.com/package/mint).
     </Info>
 
-    ``` {2}
+    ```bash {2}
     /your-project
       |- docs.json
       |- openapi.json

api-playground/troubleshooting.mdx

@@ -37,7 +37,7 @@ If your API pages aren't displaying correctly, check these common configuration
 
     Here's an example of how things might go wrong:
 
-    ```md get-user.mdx
+    ```mdx get-user.mdx
     ---
     openapi: "GET /users/{id}/"
     ---
@@ -56,7 +56,7 @@ If your API pages aren't displaying correctly, check these common configuration
     in the `openapi` field, ensure the filename is correct. For example, if you have two OpenAPI
     documents `openapi/v1.json` and `openapi/v2.json`, your metadata might look like this:
 
-    ```md api-reference/v1/users/get-user.mdx
+    ```mdx api-reference/v1/users/get-user.mdx
     ---
     openapi: "v1 GET /users/{id}"
     ---
@@ -73,4 +73,4 @@ If your API pages aren't displaying correctly, check these common configuration
     likely require you to configure CORS on your server, as these requests will now come directly
     from your users' browsers.
   </Accordion>
-</AccordionGroup>
+</AccordionGroup>

authentication-personalization/overview.mdx

@@ -125,7 +125,7 @@ Restrict which pages are visible to your users by adding `groups` fields to your
 
 Users will only see pages for `groups` that they are in.
 
-```md
+```mdx
 ---
 title: "Managing your users"
 description: "Adding and removing users from your organization"