WIP-comments-resolved

Author: aditya520

pages/express-relay/_meta.json

@@ -25,14 +25,16 @@
 
   "api-reference": {
     "title": "HTTP API Reference ↗",
-    "href": "https://pyth-express-relay-mainnet.asymmetric.re/docs/"
+    "href": "https://pyth-express-relay-mainnet.asymmetric.re/redoc/",
+    "newWindow": true
   },
   "websocket-api-reference": "Websocket API Reference",
   "contract-addresses": "Contract Addresses",
   "errors": "Error Codes",
   "examples": {
     "title": "Example Application ↗",
-    "href": "https://github.com/pyth-network/pyth-crosschain/tree/main/express_relay/examples/easy_lend"
+    "href": "https://github.com/pyth-network/pyth-crosschain/tree/main/express_relay/examples/easy_lend",
+    "newWindow": true
   },
   "-- Understand Express Relay": {
     "title": "Understanding Express Relay",

pages/express-relay/integrate-as-protocol.mdx

@@ -74,7 +74,7 @@ require(
 );
 ```
 <Callout type="info" emoji="ℹ️">
-  The `permissionId` represents unique identifying information of an opportunity. 
+  The `permissionId` represents a unique identifier of an opportunity. 
   For a liquidation opportunity, the vault address or ID could be concatenated into `bytes` format. 
   Consult [`Permissioning`](./how-express-relay-works/permissioning.mdx) for more information on generating permission IDs. 
 </Callout>
@@ -202,7 +202,7 @@ The JSON payload should contain opportunities in the following format:
 
 
 Each protocol integrated with Express Relay must actively monitor for new opportunities.
-You can do this by indexing the chain, listening to protocol events, or querying protocol state through an RPC provider.
+Protocols can do this by indexing the chain, listening to protocol events, or querying protocol state through an RPC provider.
 
 Check the [`monitor.ts`](https://github.com/pyth-network/pyth-crosschain/blob/main/express_relay/examples/easy_lend/src/monitor.ts) script,
 which fetches opportunities for the below-mentioned [Easy Lend](https://github.com/pyth-network/pyth-crosschain/tree/main/express_relay/examples/easy_lend) example and exposes them to Express Relay for auction.

pages/express-relay/integrate-as-searcher.mdx

@@ -15,9 +15,9 @@ Searchers can integrate with Express Relay in three steps:
 
 <Steps>
 
-### Subscribe to new opportunities
+### Subscribe to new Opportunities
 
-Express Relay provides searchers with `Typescript` and `Python` SDKs to interact with Express Relay. 
+Express Relay provides searchers with [`Typescript`](https://github.com/pyth-network/pyth-crosschain/tree/main/express_relay/sdk/js) and [`Python`](https://github.com/pyth-network/pyth-crosschain/tree/main/express_relay/sdk/python) SDKs to interact with Express Relay. 
 Searchers can also directly fetch available opportunities via HTTP or subscribe to them via WebSocket.
 
 <Tabs items={['Typescript', 'Python', 'HTTP', 'Websocket']}>
@@ -119,7 +119,7 @@ The server responds with opportunities in the following format:
 }
 ```
 
-### Evaluate the opportunity and construct the bid
+### Evaluate the Opportunity and Construct the Bid
 
 Searchers should construct a bid based on the fetched opportunity.
 The SDKs provide an easy way to construct a bid using the [`OpportunityAdapter`](./integrate-as-searcher/opportunity-adapter.mdx) contract. 
@@ -173,7 +173,7 @@ def opportunity_callback(opportunity: Opportunity):
 
 If you prefer to use your own custom contracts instead of the `OpportunityAdapter`, please refer to the [custom contracts](./integrate-as-searcher/custom-contract.mdx) section.
 
-### Submit bids on opportunities to Express Relay
+### Submit Bids on Opportunities to Express Relay
 
 Searchers can submit the constructed bids to Express Relay via the SDKs, an HTTP POST request, or a WebSocket connection.
 

pages/express-relay/integrate-as-searcher/opportunity-adapter.mdx

@@ -20,7 +20,7 @@ Refer to the following command to deposit native ETH to `WETH`:
 ```bash copy
 cast send \
 --private-key $PRIVATE_KEY \
---rpc-url https://sepolia.optimism.io/  \
+--rpc-url https://mainnet.mode.network/  \
 $WETH_ADDRESS \
 "deposit()" --value 0.1ether # Change the value to the amount you want to deposit
 ```
@@ -35,7 +35,7 @@ Refer to the following command to approve a token to `Permit2`:
 ```bash copy
 cast send \
 --private-key $PRIVATE_KEY \
---rpc-url https://sepolia.optimism.io/  \
+--rpc-url https://mainnet.mode.network/  \
 $TOKEN_ADDRESS \
 "approve(address spender, uint256 value)" \
 0x000000000022D473030F116dDEE9F6B43aC78BA3 100000000000000000000000000 # You can use a large amount to avoid approving multiple times