quick fix to improve the OpenAPI pages

api-playground/openapi/setup.mdx

@@ -49,6 +49,8 @@
 }
 ```
 
+<Note>The directory field is optional. If not specified, the files will be placed in the **api-reference** folder of the docs repo.</Note>
+
 When using this option, the metadata for the generated pages will have the following default values:
 
 * `title`: The `summary` field from the OpenAPI operation, if present. Otherwise a title generated from the HTTP method and endpoint.
@@ -77,6 +79,8 @@
 If you have multiple OpenAPI files, include the path to the OpenAPI file to ensure Mintlify finds the correct OpenAPI document. This is not required if you have
 only one OpenAPI file - it will automatically detect your OpenAPI file.
 
+If you want to reference an external OpenAPI file using this method, provide the file’s URL in the docs.json. See [here](https://mintlify.com/docs/settings/global#param-source-4) for the correct format.
+
 <CodeGroup>
   ```md Example
   ---
@@ -93,8 +97,6 @@
   ```
 </CodeGroup>
 
-<br />
-
 <Note>
   In most cases, the method and path must match the method and path specified
   in the OpenAPI document exactly. If the endpoint doesn't exist in the OpenAPI
@@ -104,12 +106,12 @@
   and the correct method will be generated.
 </Note>
 
 ### Autogenerate files
 
 For large OpenAPI documents, creating one MDX page for each OpenAPI operation can be a lot of work. To make it easier, we created a local OpenAPI page scraper.
 
 Our Mintlify [scraper](https://www.npmjs.com/package/@mintlify/scraping)
 autogenerates MDX files for your OpenAPI endpoints.
 
 Each generated page will correspond to an OpenAPI operation under the "paths" section of the OpenAPI schema.
 If your OpenAPI document is version 3.1+, the scraper will also generate pages for webhooks under the "webhooks" section of the OpenAPI schema.
@@ -134,7 +136,7 @@
 reorder and add the files to your navigation manually.
 
 <Note>
   If your OpenAPI document is invalid, the files will not autogenerate.
 </Note>
 
 

api-playground/troubleshooting.mdx

@@ -16,7 +16,7 @@ Here's a list of common issues we've seen customers run into:
 
     To verify your OpenAPI document will pass validation:
 
-    1. Visit [this validator](https://apitools.dev/swagger-parser/online/)
+    1. Visit [this validator](https://editor.swagger.io/)
     2. Switch to the "Validate text" tab
     3. Paste in your OpenAPI document
     4. Click "Validate it!"