introduced next steps

Author: krofax

pages/stack/operators/features/proxyd.mdx

@@ -4,6 +4,8 @@ lang: en-US
 description: Learn about the proxyd service and how to configure it for use in the OP Stack.
 ---
 
+import { Steps } from 'nextra/components'
+
 # proxyd
 
 `proxyd` is an important RPC request router and proxy used within the OP Stack infrastructure. It enables operators to efficiently route and manage RPC requests across multiple backend services, ensuring performance, fault tolerance, and security.
@@ -19,37 +21,57 @@ description: Learn about the proxyd service and how to configure it for use in t
 *   Caching of immutable responses
 *   Metrics for request latency, error rates, and backend health
 
-
-## Usage
+## How it works
 
 To start using `proxyd`, follow these steps:
 
-1.  **Build the Binary**:
-    ```bash
-    make proxyd  
-    ```
+<Steps>
+  ### **Build the Binary**:
+
+  *   Run the following command to build the `proxyd` binary:
+      ```bash
+      make proxyd
+      ```
+  *   This will build the `proxyd` binary. No additional dependencies are required.
 
-This will build the proxyd binary. No additional dependencies are required.
+  ### **Configure `proxyd`**:
 
-2.  Configure `proxyd`: Create a configuration file to define your proxy backends and routing rules. Refer to [example.config.toml](https://github.com/ethereum-optimism/infra/blob/main/proxyd/example.config.toml) for a full list of options with commentary.
+  *   Create a configuration file to define your proxy backends and routing rules.
+  *   Refer to [example.config.toml](https://github.com/ethereum-optimism/infra/blob/main/proxyd/example.config.toml) for a full list of options with commentary.
 
-3.  Start the Service: Once the configuration file is ready, start the proxyd service using:
+  ### **Start the Service**:
 
-```
-proxyd <path-to-config>.toml
-```
+  Once the configuration file is ready, start the `proxyd` service using the following command:
+
+  ```bash
+  proxyd <path-to-config.toml>
+  ```
+</Steps>
 
 ## Consensus Awareness
-Version 4.0.0 and later include consensus awareness to minimize chain reorganizations. Set `consensus_aware` to `true` in the configuration to enable:
+
+Version 4.0.0 and later include consensus awareness to minimize chain reorganizations.
+
+Set `consensus_aware` to `true` in the configuration to enable:
+
 *   Polling backends for consensus data (latest block, safe block, peer count, etc.).
 *   Resolving consensus groups based on healthiest backends
 *   Enforcing consensus state across client requests
 
 ## Caching and Metrics
 
 ### Cacheable Methods
+
 Certain immutable methods, such as `eth_chainId` and `eth_getBlockByHash`, can be cached using Redis to optimize performance.
 
 ### Metrics
+
 Extensive metrics are available to monitor request latency, error rates, backend health, and more. These can be configured via `metrics.port` and `metrics.host` in the configuration file.
 
+## Next Steps
+
+*   Read about the [OP Stack chain architecture](/builders/chain-operators/architecture).
+*   Find out how you can support [snap sync](/builders/chain-operators/management/snap-sync).
+    on your chain.
+*   Find out how you can utilize [blob space](/builders/chain-operators/management/blobs)
+    to reduce the transaction fee cost on your chain.