Name MoqTransport as the JavaScript class in the MoQ guide

Author: mattshep

llms-full.txt

@@ -31836,7 +31836,7 @@ The basic flow is handled for you, allowing you to focus on building your agent'
 # Pipecat Cloud Media over QUIC
 Source: https://docs.pipecat.ai/pipecat-cloud/guides/moq.md
 
-Run Pipecat Cloud agents over Media over QUIC: start a session with transport moq, connect MoqTransport, and use MOQSessionArguments.
+Pipecat Cloud agents over Media over QUIC: /start with transport moq, the JavaScript MoqTransport, and MOQSessionArguments in the bot.
 
 Media over QUIC (MoQ) connects a browser to your Pipecat Cloud agent through the MoQ relays in the agent's region. The browser's audio and RTVI messages travel over WebTransport, with a WebSocket fallback, and your agent reaches the region's relays from inside Pipecat Cloud. Pipecat Cloud runs the relays and issues each session's credentials, so there is no relay to deploy and no token to mint.
 
@@ -31925,7 +31925,7 @@ A MoQ session has no Daily room and no ICE servers, so `createDailyRoom` and `en
 
 ## Connecting from the browser
 
-`MoqTransport` reads the `/start` response's `moq` block itself, so `startBotAndConnect()` can call `/start` and connect in one step:
+The JavaScript SDK's `MoqTransport` reads the `/start` response's `moq` block itself, so `startBotAndConnect()` can call `/start` and connect in one step:
 
 ```javascript
 import { PipecatClient } from "@pipecat-ai/client-js";
@@ -31972,7 +31972,7 @@ A `/start` with `transport: "moq"` can be refused before any session starts. The
     icon="js"
     href="/api-reference/client/js/transports/moq"
   >
-    `MoqTransport` options, events and connection states.
+    The JavaScript `MoqTransport`: options, events and connection states.
   </Card>
   <Card
     title="MoQ transport (server)"

llms.txt

@@ -234,7 +234,7 @@ LLM, transports, serializers), pipelines, frames, workers, and utilities.
 - [Pipecat Cloud Capacity Planning](https://docs.pipecat.ai/pipecat-cloud/guides/capacity-planning.md): Plan Pipecat Cloud capacity to minimize cold starts: auto-scaling behavior, the min-agents parameter, and sizing for call volume.
 - [Pipecat Cloud Personal Access Tokens](https://docs.pipecat.ai/pipecat-cloud/guides/personal-access-tokens.md): Authenticate CI/CD pipelines and automation against Pipecat Cloud with non-interactive personal access tokens (PATs).
 - [Pipecat Cloud Daily WebRTC](https://docs.pipecat.ai/pipecat-cloud/guides/daily-webrtc.md): Use Daily as the WebRTC transport for Pipecat Cloud agents: room creation, tokens, and connecting clients to agent sessions.
-- [Pipecat Cloud Media over QUIC](https://docs.pipecat.ai/pipecat-cloud/guides/moq.md): Run Pipecat Cloud agents over Media over QUIC: start a session with transport moq, connect MoqTransport, and use MOQSessionArguments.
+- [Pipecat Cloud Media over QUIC](https://docs.pipecat.ai/pipecat-cloud/guides/moq.md): Pipecat Cloud agents over Media over QUIC: /start with transport moq, the JavaScript MoqTransport, and MOQSessionArguments in the bot.
 - [Krisp VIVA on Pipecat Cloud](https://docs.pipecat.ai/pipecat-cloud/guides/krisp-viva.md): Enable Krisp VIVA voice isolation on Pipecat Cloud to remove background noise and voices for more reliable agent conversations.
 
 #### Logging & Observability

pipecat-cloud/guides/moq.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Pipecat Cloud Media over QUIC"
 sidebarTitle: "Media over QUIC (MoQ)"
-description: "Run Pipecat Cloud agents over Media over QUIC: start a session with transport moq, connect MoqTransport, and use MOQSessionArguments."
+description: "Pipecat Cloud agents over Media over QUIC: /start with transport moq, the JavaScript MoqTransport, and MOQSessionArguments in the bot."
 ---
 
 Media over QUIC (MoQ) connects a browser to your Pipecat Cloud agent through the MoQ relays in the agent's region. The browser's audio and RTVI messages travel over WebTransport, with a WebSocket fallback, and your agent reaches the region's relays from inside Pipecat Cloud. Pipecat Cloud runs the relays and issues each session's credentials, so there is no relay to deploy and no token to mint.
@@ -91,7 +91,7 @@ A MoQ session has no Daily room and no ICE servers, so `createDailyRoom` and `en
 
 ## Connecting from the browser
 
-`MoqTransport` reads the `/start` response's `moq` block itself, so `startBotAndConnect()` can call `/start` and connect in one step:
+The JavaScript SDK's `MoqTransport` reads the `/start` response's `moq` block itself, so `startBotAndConnect()` can call `/start` and connect in one step:
 
 ```javascript
 import { PipecatClient } from "@pipecat-ai/client-js";
@@ -138,7 +138,7 @@ A `/start` with `transport: "moq"` can be refused before any session starts. The
     icon="js"
     href="/api-reference/client/js/transports/moq"
   >
-    `MoqTransport` options, events and connection states.
+    The JavaScript `MoqTransport`: options, events and connection states.
   </Card>
   <Card
     title="MoQ transport (server)"