fix nav and typos

Author: zknill

src/data/nav/aitransport.ts

@@ -16,14 +16,14 @@ export default {
           link: '/docs/ai-transport',
           index: true,
         },
+      ],
+    },
+    {
+      name: 'Token streaming',
+      pages: [
         {
-          name: 'Token streaming',
-          pages: [
-            {
-              name: 'Message per response',
-              link: '/docs/ai-transport/features/token-streaming/message-per-response',
-            },
-          ],
+          name: 'Message per response',
+          link: '/docs/ai-transport/features/token-streaming/message-per-response',
         },
       ],
     },

src/pages/docs/ai-transport/features/token-streaming/message-per-response.mdx

@@ -29,7 +29,7 @@ This approach is ideal when:
    action to the Ably channel with an empty or the first token as content.
 2. **Token streaming**: Append subsequent tokens to the original message by publishing those tokens
    with the `message.append` action.
-3. **Live Delivery**: Clients subscribed to the channel receive each appended token in real-time, allowing
+3. **Live Delivery**: Clients subscribed to the channel receive each appended token in realtime, allowing
    them to progressively render the response.
 4. **Compacted history**: The channel history contains only one message per AI response,
    which includes all tokens appended to it concatenated together.
@@ -129,7 +129,7 @@ Subscribers receive different message actions depending on when they join and ho
 messages.
 
 When subscribed to a channel, clients receive the initial message with the `message.create` action,
-followed by each token as a `message.append` action in real-time.
+followed by each token as a `message.append` action in realtime.
 
 <Code>
 ```javascript