chore(lazer) How lazer works requested changes

Author: aditya520

pages/lazer/how-lazer-works.mdx

@@ -1,13 +1,12 @@
-import { Callout } from "nextra/components";
-
 # How Pyth Lazer works
 
 Pyth Lazer is a permissioned service that provides ultra-low-latency market data to consumers.
 It aggregates data from multiple publishers and distributes it to consumers through a multi-tier architecture.
 
 ## System Services
 
-The architecture consists of five main services that work together to provide ultra-low-latency data to consumers.
+The architecture consists of five main types of services that work together to provide ultra-low-latency data to consumers.
+Each service has multiple instances running to ensure high availability and low latency.
 
 ### INSERT DIAGRAM HERE
 
@@ -23,33 +22,30 @@ The Relayer service is the ingestion layer that receives and validates all incom
 **Key responsibilities:**
 
 - **Authentication**: Validates publisher access tokens and optional Ed25519 signatures.
+- **Validation**: Performs sanity checks on incoming updates by examining feed IDs, timestamps, and values to ensure data integrity and proper formatting.
 - **Rate limiting**: Enforces configurable limits on publisher updates.
-- **Message forwarding**: Publishes validated updates to an internal message queue (a NATS cluster).
+- **Message forwarding**: Publishes validated updates to an internal message queue.
 
-**Douro Labs** operates the relayer service for the Pyth Lazer network.
+Douro Labs operates the relayer service for the Pyth Lazer network. It follows a strict, deterministic processing model:
 
-<Callout type="info">
-  The Douro Labs-operated relayer follows a strict, deterministic processing model:
-  - **No price dropping**: All validated updates are forwarded to the message queue without dropping any prices.
-  - **FCFS processing**: Updates are processed on a first-come-first-served basis without prioritization.
-  - **Deterministic operation**: The relayer operates according to its configured logic and does not deviate from it.
+- **No price dropping outside of circuit breakers**: All validated updates are forwarded to the message queue without dropping any prices.
+- **FCFS processing**: Updates are processed on a first-come-first-served basis without prioritization.
+- **Deterministic operation**: The relayer operates according to its configured logic and does not deviate from it.
 
 This ensures reliable, predictable data flow from publishers to consumers.
 
-</Callout>
-
 ### Message Queue
 
-The system uses NATS JetStream as the primary message queue for pub/sub messaging with stream persistence.
+The system uses a distributed message queue for pub/sub messaging with stream persistence.
 This allows the system to be deployed in a multi-datacenter environment and ensures reliable message delivery between services.
 
-**Message ordering**: NATS JetStream guarantees message ordering within a single stream, ensuring that updates from publishers are processed in the order they were received by the Relayer.
+**Message ordering**: The message queue guarantees message ordering within a single stream, ensuring that updates from publishers are processed in the order they were received by the Relayer.
 This ordering guarantee is critical for maintaining consistent feed state across all aggregators.
 
 ### Routers
 
 The Router is the real-time distribution layer that serves data to consumers.
-It embeds aggregation logic to compute median prices, confidence intervals (using interquartile range), and best bid/ask prices from multiple publisher inputs.
+It embeds aggregation logic to compute median prices, confidence intervals (using interquartile range), and best bid/ask prices, funding rates, and more from multiple publisher inputs.
 
 **Key features:**
 
@@ -60,7 +56,7 @@ It embeds aggregation logic to compute median prices, confidence intervals (usin
 
 #### Aggregation logic
 
-Each Router embeds an aggregator component that consumes publisher updates from NATS and computes aggregated data feeds. The aggregator:
+Each Router embeds an aggregator component that consumes publisher updates from the Message Queue and computes aggregated data feeds. The aggregator:
 
 - Computes median values resistant to outlier data from individual publishers.
 - Calculates confidence intervals using interquartile range to measure data spread.
@@ -73,5 +69,5 @@ The History Service provides persistence and historical data queries.
 
 **Key responsibilities:**
 
-- Data persistence: Stores all publisher updates, aggregated data, and transactions in ClickHouse.
+- Data persistence: Stores all publisher updates, aggregated data, and transactions.
 - Historical queries: Provides REST API for querying historical data.