update docs

Author: lawreka

api-playground/asyncapi/playground.mdx

@@ -3,7 +3,7 @@ title: "Websockets Playground"
 description: "Enable users to interact with your websockets"
 ---
 
-Autogenerating pages from your AsyncAPI spec will create pages for each channel that display message data that can be sent and received. In the API Playground for websockets, you can connect to websocket servers to send and receive messages.
+Autogenerating pages from your AsyncAPI schema will create pages for each channel that display message data that can be sent and received. In the API Playground for websockets, you can connect to websocket servers to send and receive messages.
 
 ![](https://picsum.photos/600/400)
 (this should be a nice image of messages in the API playground)

api-playground/asyncapi/setup.mdx

@@ -5,12 +5,12 @@ description: "Reference AsyncAPI endpoints in your docs pages"
 
 ## Add an AsyncAPI specification file
 
-To begin to create pages for your websockets, make sure you have a valid AsyncAPI document in either JSON or YAML format that follows the [AsyncAPI specification](https://www.asyncapi.com/docs/reference/specification/v3.0.0). Your document must follow AsyncAPI specification 3.0+.
-<Tip>To make sure your AsyncAPI spec is valid, you can paste it into the [AsyncAPI Studio](https://studio.asyncapi.com/)</Tip>
+To begin to create pages for your websockets, make sure you have a valid AsyncAPI schema document in either JSON or YAML format that follows the [AsyncAPI specification](https://www.asyncapi.com/docs/reference/specification/v3.0.0). Your schema must follow AsyncAPI specification 3.0+.
+<Tip>To make sure your AsyncAPI schema is valid, you can paste it into the [AsyncAPI Studio](https://studio.asyncapi.com/)</Tip>
 
 ## Auto-populate websockets pages
 
-You can add an `asyncapi` field to any tab or group in the navigation of your `docs.json`. This field can contain either the path to an AsyncAPI document in your docs repo, or the URL of a hosted AsyncAPI document. Mintlify will automatically generate a page for each AsyncAPI webhook channel.
+You can add an `asyncapi` field to any tab or group in the navigation of your `docs.json`. This field can contain either the path to an AsyncAPI schema document in your docs repo, the URL of a hosted AsyncAPI schema document, or an array of links to AsyncAPI schema documents. Mintlify will automatically generate a page for each AsyncAPI websocket channel.
 
 **Examples with Tabs:**
 ```json {5}
@@ -29,11 +29,11 @@ You can add an `asyncapi` field to any tab or group in the navigation of your `d
 "navigation": {
   "tabs": [
     {
-      "tab": "API Reference",
+      "tab": "AsyncAPI",
       "groups": [
         {
-          "group": "Endpoints",
-          "openapi": {
+          "group": "Websockets",
+          "asyncapi": {
             "source": "/path/to/asyncapi.json",
             "directory": "api-reference"
           }
@@ -46,4 +46,4 @@ You can add an `asyncapi` field to any tab or group in the navigation of your `d
 
 <Note>The directory field is optional. If not specified, the files will be placed in the **api-reference** folder of the docs repo.</Note>
 
-The metadata for the generated pages will contain the key `asyncapi` with a path to the original spec and the channel id so that the page can be generated per channel and display data about all websocket messages sent and received on that channel.
+The metadata for the generated pages will contain the key `asyncapi` with a path to the original spec and the channel id so that the page can be generated per channel and display data about all websocket messages sent and received on that channel. Learn more about interacting with websockets with generated AsyncAPI pages in the playground [here](api-playground/asyncapi/playground).