Tidy up commit

Author: franrob-projects

src/pages/docs/platform/architecture/edge-network.mdx

@@ -33,7 +33,7 @@ Behind CloudFront, each Ably region employs AWS Network Load Balancers to distri
 
 Ably uses DNS-based latency routing to direct clients to the nearest available datacenter. The primary endpoints for client connections and HTTP requests is `main.realtime.ably.net`.
 
-When a client performs a DNS lookup for this endpoint, the DNS service resolves to the closest datacenter, among those that are currently enabled, to the client's location. This latency-based routing ensures that clients connect to the datacenter with the lowest network latency, maximising the responsiveness of the service.
+When a client performs a DNS lookup for this endpoint, the DNS service resolves to the closest datacenter, among those that are currently enabled, to the client's location. This latency-based routing ensures that clients connect to the datacenter with the lowest network latency, maximizing the responsiveness of the service.
 
 Ably's DNS configuration uses a TTL of 60 seconds, allowing for relatively quick rerouting of traffic if a datacenter becomes unhealthy. The health of each datacenter is continuously monitored, and if issues are detected, Ably can modify the DNS routing to direct traffic away from the affected datacenter within minutes.
 
@@ -111,9 +111,9 @@ The geographic distribution of these access points is continuously reviewed and
 
 #### China connectivity
 
-Ably's service works in China, with customers successfully using the platform to serve users globally, including within China. The extensive global network with over 700 edge locations provides connectivity to Chinese users.
+Ably's service works in China, with customers successfully using the platform to serve users globally, including within China. The global network with over 700 edge locations provides connectivity to Chinese users.
 
-However, China operates a national firewall that can block access to foreign websites and services without notice. While Ably is not currently aware of any blocks affecting its services, potential firewall changes could impact service availability. Ably has implemented specific strategies to ensure reliable service in China, including partnerships with local providers, alternative routing arrangements, and region-specific optimizations.
+China operates a national firewall that can block access to foreign websites and services without notice. While Ably is not currently aware of any blocks affecting its services, potential firewall changes could impact service availability. Ably has implemented specific strategies to ensure reliable service in China, including partnerships with local providers, alternative routing arrangements, and region-specific optimizations.
 
 ### Protocol support and transport optimization
 

src/pages/docs/platform/architecture/index.mdx

@@ -14,20 +14,20 @@ Ably's globally distributed infrastructure forms the foundation of the platform,
 
 Ably characterizes the system across [4 pillars of dependability](https://ably.com/four-pillars-of-dependability):
 
-* **Performance**: Ably focuses on predictability of latencies to provide certainty in uncertain operating conditions.
+* Performance: Focuses on predictability of latencies to provide certainty in uncertain operating conditions.
   * `<30ms` round trip latency within datacenter (99th percentile)
   * `<65ms` global round trip latency (99th percentile)
-* **Integrity**: Guarantees for message ordering and delivery.
+* Integrity: Guarantees for message ordering and delivery.
   * Exactly-once delivery semantics
   * Guaranteed message ordering from publishers to subscribers
   * Automatic connection recovery with message continuity
-* **Reliability**: Fault tolerant architecture at regional and global levels to survive multiple failures without outages.
+* Reliability: Fault tolerant architecture at regional and global levels to survive multiple failures without outages.
   * 100% message delivery guarantee through multi-region redundancy
   * 99.999999% message survivability
   * 99.99999999% persisted data survivability
   * Edge network failure resolution by the client SDKs within 30s
   * Automated routing of all traffic away from an abrupt failure of datacenter in less than two minutes
-* **Availability**: Meticulously designed to provide continuity of service even in the case of instance or whole datacenter failures.
+* Availability: Designed to provide continuity of service even in the case of instance or whole datacenter failures.
   * 99.999% global service availability (5 minutes 15 seconds of downtime per year)
   * 50% global capacity margin for instant demand surges
 
@@ -37,12 +37,12 @@ Ably's platform is a global service that supports all realtime messaging and ass
 
 The platform has been designed with the following primary objectives in mind:
 
-* **Horizontal scalability**: As more nodes are added, load is automatically redistributed across the cluster so that global capacity increases linearly with the number of instances Ably runs.
-* **No single point of congestion**: As the system scales, there is no single point of congestion for any data path, and data within the system is routed peer-to-peer, ensuring no single component becomes overloaded as traffic scales for an individual app or across the cluster.
-* **Fault tolerance**: Faults in the system are expected, and the system must have redundancy at every layer in the stack to ensure availability and reliability.
-* **Autonomy**: Each component in the system should be able to operate fully without reliance on a global controller. For example, two isolated data centers should continue to service realtime requests while isolated.
-* **Consistent low latencies**: Within data centers, Ably aims for latencies to be in the low 10s of milliseconds and less than 100ms globally. Consistently achieving low latencies requires careful consideration of the placement of data and services across the system as well as prioritisation of the computation performed by each service.
-* **Quality of service**: Ably intentionally designs for high QoS targets to enable sophisticated realtime applications that would be impossible on platforms with weaker guarantees.
+* Horizontal scalability: As more nodes are added, load is automatically redistributed across the cluster so that global capacity increases linearly with the number of instances.
+* No single point of congestion: As the system scales, there is no single point of congestion for any data path, and data within the system is routed peer-to-peer, ensuring no single component becomes overloaded as traffic scales for an individual app or across the cluster.
+* Fault tolerance: Faults in the system are expected, and the system must have redundancy at every layer in the stack to ensure availability and reliability.
+* Autonomy: Each component in the system should be able to operate fully without reliance on a global controller. For example, two isolated data centers should continue to service realtime requests while isolated.
+* Consistent low latencies: Within data centers, latencies are in the low 10s of milliseconds and less than 100ms globally. Consistently achieving low latencies requires careful consideration of the placement of data and services across the system as well as prioritisation of the computation performed by each service.
+* Quality of service: Designed for high QoS targets to enable sophisticated realtime applications that would be impossible on platforms with weaker guarantees.
 
 ## Cluster architecture
 
@@ -52,10 +52,10 @@ Each regional deployment operates independently, handling its own subscriber con
 
 Ably's architecture consists of four primary layers:
 
-* **Routing Layer**: Provides intelligent, latency optimized routing for robust end client connectivity.
-* **Gossip Layer**: Distributes network topology information and facilitates service discovery.
-* **Frontend Layer**: Handles REST requests and maintains realtime connections (such as WebSocket, Comet and SSE).
-* **Core Layer**: Performs all central message processing for channels.
+* Routing Layer: Provides intelligent, latency optimized routing for robust end client connectivity.
+* Gossip Layer: Distributes network topology information and facilitates service discovery.
+* Frontend Layer: Handles REST requests and maintains realtime connections (such as WebSocket, Comet and SSE).
+* Core Layer: Performs all central message processing for channels.
 
 ![Ably Architecture Overview Diagram](../../../../images/content/diagrams/architecture-overview.png)
 
@@ -144,5 +144,5 @@ Once a message is acknowledged, it is stored in multiple physical locations, pro
 
 Messages are stored in two ways:
 
-* **Ephemeral Storage**: Messages are held for 2 minutes in an in-memory database (Redis). This data is distributed according to Ably's consistent hashing mechanism and relocated when channels move between nodes. This short-term storage enables low-latency message delivery and retrieval and supports features like [connection recovery](/docs/connect/states).
-* **Persisted Storage**: Messages can optionally be stored persistently on disk if longer term retention is required. Ably uses a globally distributed and clustered database (Cassandra) for this purpose, deployed across multiple data centers with message data replicated to three regions to ensure integrity and availability even if a region fails.
+* Ephemeral Storage: Messages are held for 2 minutes in an in-memory database (Redis). This data is distributed according to the consistent hashing mechanism and relocated when channels move between nodes. This short-term storage enables low-latency message delivery and retrieval and supports features like [connection recovery](/docs/connect/states).
+* Persisted Storage: Messages can optionally be stored persistently on disk if longer term retention is required. Uses a globally distributed and clustered database (Cassandra) for this purpose, deployed across multiple data centers with message data replicated to three regions to ensure integrity and availability even if a region fails.

src/pages/docs/platform/architecture/performance.mdx

@@ -23,7 +23,7 @@ The first objective is minimizing latency and latency variance for message deliv
 
 The second objective is maximizing single-channel throughput in terms of both message rate and bandwidth. This ensures that even when a channel handles high volumes of traffic, such as during live events or peak usage periods, the system can efficiently process and distribute messages without degradation.
 
-Ably achieves a [**global mean latency of 37ms**](/docs/platform/architecture/latency) to provide the best possible realtime experience to your users.
+Ably achieves a [global mean latency of 37ms](/docs/platform/architecture/latency).
 
 Beyond average latency, Ably focuses on the performance of the slowest percentiles of messages (p95, p99, p99.9) to ensure consistent performance for all messages. These tail latencies often reveal performance issues that might be hidden by average measurements.
 

src/pages/docs/protocols/mqtt.mdx

@@ -19,7 +19,6 @@ Behind the scenes, the adapter just uses the normal Ably service, so there is no
 MQTT is recommended to interact with Ably when:
 
 * Bandwidth is limited and you want to keep network traffic to a minimum
-* You want to keep network traffic to a minimum.
 
 ## Known limitations <a id="limitations"/>