remove duplicate API troubleshooting info

Author: ethanpalm

api-playground/troubleshooting.mdx

@@ -4,8 +4,7 @@ description: "Common issues with API References"
 icon: "message-square-warning"
 ---
 
-API pages are complicated. As a result, there are a lot of things that can go wrong.
-Here's a list of common issues we've seen customers run into:
+If your API pages aren't displaying correctly, check these common configuration issues:
 
 <AccordionGroup>
   <Accordion title="All of my OpenAPI pages are completely blank">

support.mdx

@@ -34,69 +34,6 @@ export function openSearch(e) {
 
 <AccordionGroup>
 
-  <Accordion title="API page issues" icon="book-open">
-    API pages are complicated. As a result, there are a lot of things that can go wrong. Here's a list of common issues we've seen customers run into:
-
-    <AccordionGroup>
-      <Accordion title="All of my OpenAPI pages are completely blank">
-        In this scenario, it's likely that either Mintlify cannot find your OpenAPI document or your OpenAPI document is invalid.
-
-        Running `mint dev` locally should reveal some of these issues.
-
-        To verify your OpenAPI document will pass validation:
-
-        1. Run `mint openapi-check <openapiFilenameOrUrl>` in your CLI.
-        2. Validate your OpenAPI spec with [Swagger Editor](https://editor.swagger.io/).
-
-        Additionally, Mintlify does not support OpenAPI 2.0. If your document uses OpenAPI 2.0, you may encounter this issue. You can convert your document with [Swagger Editor](https://editor.swagger.io/).
-
-        <Frame>
-          !["Convert to OpenAPI 3" menu item highlighted in the Swagger Editor](/images/convert-oas-3.png)
-        </Frame>
-      </Accordion>
-      <Accordion title="One of my OpenAPI pages is completely blank">
-        This is usually caused by a misspelled `openapi` field in the page metadata. Make sure that the HTTP method and path match the HTTP method and path in the OpenAPI document exactly.
-
-        Here's an example of how things might go wrong:
-
-        ```md get-user.mdx
-        ---
-        openapi: "GET /users/{id}/"
-        ---
-        ```
-
-        ```yaml openapi.yaml
-        paths:
-          "/users/{id}":
-            get: ...
-        ```
-        Notice that the path in the `openapi` field has a trailing slash, whereas the path in the OpenAPI
-        document does not.
-
-        Another common issue is a misspelled filename. If you are specifying a particular OpenAPI document
-        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
-        ---
-        openapi: "v1 GET /users/{id}"
-        ---
-        ```
-      </Accordion>
-      <Accordion title="Requests from the API Playground don't work">
-        If you have a custom domain configured, this could be an issue with your reverse proxy. By
-        default, requests made via the API Playground start with a `POST` request to the
-        `/api/request` path on the docs site. If your reverse proxy is configured to only allow `GET`
-        requests, then all of these requests will fail. To fix this, configure your reverse proxy to
-        allow `POST` requests to the `/api/request` path.
-
-        Alternatively, if your reverse proxy prevents you from accepting `POST` requests, you can configure Mintlify to send requests directly to your backend with the `api.playground.proxy` setting in the `docs.json`. See the [configurations for the API playground](/settings#param-proxy) for more information. This will
-        likely require you to configure CORS on your server, as these requests will now come directly
-        from your users' browsers.
-      </Accordion>
-    </AccordionGroup>
-  </Accordion>
-
   <Accordion title="Docs page won't load (error 404)" icon="ban" iconType="regular">
     Check to see if you have `/api` in the URL. This is a reserved folder in production environments, which produces a 404 error.
   </Accordion>