upate steps

Author: ethanpalm

api-playground/mdx-setup.mdx

@@ -6,7 +6,7 @@ icon: 'markdown'
 
 You can manually define API endpoints in individual `MDX` files rather than using an OpenAPI specification. This method provides flexibility for custom content, but we recommend generating API documentation from an OpenAPI specification file for most API documentation projects as it's more maintainable and feature-rich. However, MDX can be useful for documenting small APIs, prototyping, or when you want to feature API endpoints alongside other content.
 
-To generate pages for API endpoints using `MDX`, configure your API settings in `docs.json`, create individual `MDX` files for each endpoint, and use components like <ParamFields /> to define parameters. From these definitions, Mintlify generates interactive API playgrounds, request examples, and response examples.
+To generate pages for API endpoints using `MDX`, configure your API settings in `docs.json`, create individual `MDX` files for each endpoint, and use components like `<ParamFields />` to define parameters. From these definitions, Mintlify generates interactive API playgrounds, request examples, and response examples.
 
 <Steps>
   <Step title="Configure your API">
@@ -24,7 +24,7 @@ To generate pages for API endpoints using `MDX`, configure your API settings in
     }
     ```
 
-    If you would not like to show an API playground, you don't need to include auth types. Hide the playground with the following field:
+    If you want to hide the API playground, use the `display` field. You do not need to include an auth method if you hide the playground.
 
     ```json
     "api": {
@@ -34,12 +34,12 @@ To generate pages for API endpoints using `MDX`, configure your API settings in
     }
     ```
 
-    Find a full list of API configurations [here](settings#param-api).
+    Find a full list of API configurations in [Settings](/settings#api-configurations).
   </Step>
 
   <Step title="Create your endpoint pages">
 
-    Each API endpoint page should have a corresponding MDX file. At the top of each file, define:
+    Each API endpoint page should have a corresponding `MDX` file. At the top of each file, define `title` and `api`:
 
     ```md
     ---
@@ -56,11 +56,11 @@ To generate pages for API endpoints using `MDX`, configure your API settings in
 
     <Note>
 
-    If you have `server` configured in [docs.json](settings), you can use relative paths like `/v1/endpoint`.
+    If you have a `server` field configured in `docs.json`, you can use relative paths like `/v1/endpoint`.
 
     </Note>
 
-    You can also override the globally-defined display mode for the API playground per page by adding `playground` at the top of the MDX file:
+    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
     ---
@@ -72,6 +72,6 @@ To generate pages for API endpoints using `MDX`, configure your API settings in
   </Step>
 
   <Step title="Add your endpoints to your docs">
-    Add your endpoint pages to the sidebar by adding the paths to the `navigation` field in your `docs.json`. Learn more about structuring your docs [here](navigation).
+    Add your endpoint pages to the sidebar by adding the paths to the `navigation` field in your `docs.json`. Learn more about structuring your docs in [Navigation](/navigation).
   </Step>
 </Steps>