Merge pull request #15 from primevprotocol/update-providers-section

update providers section

Author: techgangboss

get-started/providers/consume-bids-mev-commit.mdx

@@ -3,15 +3,17 @@ title: Consuming Bids from Mev-Commit
 sidebarTitle: Consuming Bids
 ---
 
-Provider nodes that have a stake in the mev-commit registry will start receiving bids on the mev-commit p2p network from bidders. In order to see the incoming bids, the providers need to communicate with the provider API using the RPC clients or the HTTP APIs. 
+Provider nodes that have a stake in the mev-commit registry will start receiving bids on the mev-commit p2p network from bidders. In order to see incoming bids, providers need to communicate with their mev-commit node using one of the available options below.
 
-Once a provider sees a bid and decides to accept or reject it, they send the status to the mev-commit node. If the bid is ACCEPTED, a signed commitment is sent back to the bidder and the mev-commit node will issue a transaction to the mev-commit chain to record the commitment. 
+Once a provider sees a bid and decides to accept or reject it, they send a status to their mev-commit node. If the bid is ACCEPTED, a signed commitment is sent back to the bidder and the provider's mev-commit node will send a transaction to the mev-commit chain to record the commitment.
 
-It is the provider's responsibility to deliver inclusion of the transactions once they make a commitment. If they win or influence the mev-boost auction and they include the transactions correctly, the bid rewards will be settled by the oracle and made available to the provider. If the bid is rejected, no commitment is made and no response is sent to the network. There is no reward or penalty for rejecting bids. The accept and reject decisioning logic is left up to the provider.
+It is the provider's responsibility to ensure inclusion of transactions on L1, relevant to accepted bids, once they make a commitment. If the provider wins the mev-boost auction and includes transactions correctly, bid amounts will be settled and rewarded to the provider.
 
-There are 4 options to communicate with the API
+If a bid is rejected by a provider, no commitment is made and no response is sent to the p2p network. There is no reward or penalty for rejecting bids, decision logic is left up to the provider.
 
-*   We recommend using the official go RPC client to communicate with the mev-commit API. In order to use this in go code, you can go get the mev-commit package and then import the generated client.
+There are 4 options for a provider to communicate with their mev-commit node
+
+*   We recommend using the official go RPC client to communicate with your mev-commit node. In order to programmatically use this client in go, you can go get the mev-commit package and then import the generated client.
 
     - For Go developers, leveraging the official Go RPC client is the recommended approach. Start by installing the mev-commit package:
 
@@ -77,7 +79,7 @@ There are 4 options to communicate with the API
     }
     ```
 
-    There is an [example implementation](https://github.com/primevprotocol/mev-commit/tree/main/examples/provideremulator) of a dummy provider client that can be found in the repository which blindly accepts all the bids it sees. This could be a good starting point for providers to use if they are trying to integrate a Golang project in.
-* Use [https://github.com/fullstorydev/grpcurl](https://github.com/fullstorydev/grpcurl) or [https://github.com/bloomrpc/bloomrpc](https://github.com/bloomrpc/bloomrpc) or other GUI clients like [Postman](https://www.postman.com). The protobuf files are available in the repository.
+    There is an [example implementation](https://github.com/primevprotocol/mev-commit/tree/main/examples/provideremulator) of a dummy provider client which blindly accepts all the bids it sees from its mev-commit node. This could be a good starting point for providers implementing their commitment decision logic in golang.
+* Use [https://github.com/fullstorydev/grpcurl](https://github.com/fullstorydev/grpcurl) or [https://github.com/bloomrpc/bloomrpc](https://github.com/bloomrpc/bloomrpc) or other GUI clients like [Postman](https://www.postman.com). Relevant protobuf files are available in the [mev-commit repository](https://github.com/primevprotocol/mev-commit).
 * Check the [API docs](https://primev-24.mintlify.app/api-reference/provider/sendprocessedbids) to use the REST APIs. The RPC APIs are also available on the HTTP server.
-* Users can use the protobuf files to generate client in language of their choice.
+* Users can use the protobuf files to generate a client in language of their choice.

get-started/providers/register-a-provider.mdx

@@ -1,8 +1,10 @@
-In order to register as a provider in the mev-commit network, you have to stake some ETH on the provider registry. This adds credibility to the commitments that you'll be issuing, as the stake may be slashed in the event of breaking a commitment, such as committing to a preconfirmation bid and not including the transaction in a block. Once the provider node is registered on the network, other nodes will connect to it and the provider node should start seeing bids come in.
+To register on the mev-commit network, providers need to stake some ether with the provider registry contract. This adds credibility to issued commitments, as stake may be slashed in the event of a broken commitment, such as committing to a preconfirmation bid and not including the relevant transaction in a block. 
+
+Once a provider is registered on the network, other nodes will connect to it and the provider node should see bids come in.
 
 You can use the provider API to check and add stake.
 
-*   Check the stake
+*   Check stake
 
     ```shell
     > curl localhost:13523/v1/provider/get_stake | jq
@@ -11,9 +13,9 @@ You can use the provider API to check and add stake.
     }
     ```
 
-    In order to stake, we need to first add funds to the Ethereum wallet created for the node on the mev-commit chain.
+    In order to stake, first fund the mev-commit chain account relevant to your node.
 
-    *   Get the wallet address of the node
+    *   Get the account address of your node
 
         ```shell
         > curl localhost:13523/topology | jq
@@ -31,7 +33,7 @@ You can use the provider API to check and add stake.
           "blocked_peers": null
         }
         ```
-    *   Add funds to the account. Currently for the testnet, you can use the Primev account to get some testnet ETH. This can be done using the cast command:
+    *   Fund your account with ether on the mev-commit chain. Currently for the testnet, you can use a faucet account to get some mev-commit chain ether. This can be done using the cast command:
 
         ```shell
         > cast send --rpc-url https://chainrpc.testnet.mev-commit.xyz \
@@ -41,14 +43,18 @@ You can use the provider API to check and add stake.
         ```
 
         This command will transfer 100 ETH on mev-commit to your `$ADDRESS` which should be enough to get started.
-*   Check the minimum amount that can be staked, and consider staking a multiple of it. Bidders will only connect to providers which have stake higher than this minimum, and the larger your stake, the greater the credibility behind your commitments. The amount is set in `wei`
+
+        Alternatively, use the bridge from Holesky to fund your account. See [bridging-and-fees](https://docs.primev.xyz/get-started/bidders/bridging-and-fees).
+
+*   Check the minimum amount that can be staked, and consider staking more than the minimum. Bidders will only connect to providers which have stake higher than this minimum. The larger a provider's stake, the greater the credibility behind that provider's commitments. The amount is set in `wei`.
 
     ```shell
     > curl localhost:13523/v1/provider/get_min_stake | jq
     {
       "amount": "1000000000000000000"
     }
     ```
+
 *   Stake
 
     ```shell
@@ -58,4 +64,4 @@ You can use the provider API to check and add stake.
     }
     ```
 
-Once you have staked, you should seeing peers getting connected in the logs within a few minutes. You can check the `/topology` endpoint again to verify that you have some connected peers.
+Once staked, peer connection logs should appear within a few minutes. You can check the `/topology` endpoint again to verify connected peers.