Edu 2071 remove the general section of faqs

src/pages/docs/basics/index.mdx

@@ -65,6 +65,7 @@ The REST interface communicates with Ably using the HTTP protocol and is effecti
 * issue tokens on behalf of other realtime clients
 * retrieve persisted messages, presence history and application usage statistics
 
+
 ### Realtime interface <a id="realtime"/>
 
 The realtime interface is implemented using an Ably-defined protocol, primarily over WebSockets. It enables clients to establish and maintain a persistent connection to Ably. The realtime interface extends the functionality of the REST interface and is most commonly used client-side. It is used to:

src/pages/docs/platform/account/app/index.mdx

@@ -22,6 +22,22 @@ If you have created apps already, your dashboard will look similar to the one sh
 
 ![Your apps in the Ably dashboard](../../../../../images/content/screenshots/dash/your-apps.png)
 
+### Environments <a id="environment"/>
+
+Each Ably app acts as a sandboxed environment, isolated from other apps in your account. This makes it straightforward to set up separate environments for development, staging, and production by creating dedicated apps for each.
+
+For example, if you're building a product called "chat-app", you could create:
+
+- `chat-app-production` for your live production environment
+- `chat-app-staging` for pre-production testing
+- `chat-app-development` for ongoing development work
+
+This approach provides complete isolation between environments, ensuring that development activities don't interfere with production traffic. An alternative approach for complete resource isolation, consider using separate Ably accounts for development and production environments. This ensures development activities cannot impact production resources under any circumstances.
+
+<Aside data-type='important'>
+Account limits are shared. While apps are sandboxed from each other, they share the same [account limits](/docs/platform/pricing/limits) such as connection counts and channel limits. A development app experiencing high usage could potentially impact your production app if account limits are reached.
+</Aside>
+
 ## App overview
 
 Your app dashboard provides the following tabs for monitoring and configuring your app settings:

src/pages/docs/platform/errors/codes.mdx

@@ -599,6 +599,7 @@ The request will be automatically retried by the SDK.
 
 **Resolution:** If the client never connects to the [primary or fallback endpoints](https://faqs.ably.com/routing-around-network-and-dns-issues), check any firewall rules that may be blocking access to Ably's [endpoints](https://faqs.ably.com/if-i-need-to-whitelist-ablys-servers-from-a-firewall-which-ports-ips-and/or-domains-should-i-add).
 
+
 ## 80016: Operation on superseded connection <a id="80016"/>
 
 This error occurs when a browser [connection](/docs/connect/states#connection-states) upgrades from an HTTP (Comet) transport to WebSockets. It is logged by the client library when operations are performed on the older transport.

src/pages/docs/platform/index.mdx

@@ -43,6 +43,7 @@ Some of the integrations available with Ably include:
 
 Use Ably's products and SDKs to build realtime applications for your clients. They all utilize Ably's reliable platform to ensure that you don't need to worry about managing things such as scaling, latency and data integrity.
 
+
 ### Ably Pub/Sub <a id="pub-sub"/>
 
 Ably's core [Pub/Sub](/docs/basics) product provides flexible APIs that are feature-rich and powerful. These flexible APIs are the building blocks for crafting any type of realtime experience for your customers.

src/pages/docs/platform/pricing/limits.mdx

@@ -60,7 +60,7 @@ Application limits relate to the quantity of resources that can be created per a
 
 ## Message limits <a id="message"/>
 
-Message limits relate to the number, rate and bandwidth of messages consumed across you account.
+Message limits relate to the number, rate and bandwidth of messages consumed across you account. Message count limits and data transfer (bandwidth) limits are enforced separately - exceeding one does not affect the other.
 
 | Message limit | Free | Standard | Pro | Enterprise |
 | ------------- | ---- | -------- | --- | ---------- |
@@ -88,6 +88,8 @@ Channel limits relate to the number, rate and membership of [channels](/docs/cha
 | **Presence members per channel with [server-side batching](/docs/messages/batch#server-side) enabled**<p>*the maximum number of clients that can be simultaneously present on a channel when server-side batching is enabled*</p> | 200 | 5,000 | 10,000 | 20,000 |
 | **Objects per channel**<p>*the maximum number of objects that can be stored on a channel*</p> | 100 | 100 | 100 | 100 |
 
+
+
 ## Connection limits <a id="connection"/>
 
 Connection limits relate to the realtime [connections](/docs/connect) made to Ably from your account.

src/pages/docs/pub-sub/index.mdx

@@ -437,6 +437,7 @@ if err := channel.Publish(context.Background(), "example", "message data"); err
 ```
 </Code>
 
+
 <Aside data-type="further-reading">
 You can find out more detail about how [channels](/docs/channels) and [messages](/docs/messages) work.