diff --git a/docs.json b/docs.json
index c787bef2..81d25f95 100644
--- a/docs.json
+++ b/docs.json
@@ -57,7 +57,6 @@
                       "v1.1.0/get-started/providers/registering-a-provider",
                       "v1.1.0/get-started/providers/consuming-bids",
                       "v1.1.0/get-started/providers/sending-commitments",
-                      "v1.1.0/get-started/providers/Querying-for-proposers",
                       "v1.1.0/get-started/providers/withdraw"
                     ]
                   }
diff --git a/v1.1.0/get-started/providers/Querying-for-proposers.mdx b/v1.1.0/get-started/providers/Querying-for-proposers.mdx
deleted file mode 100644
index 2f460170..00000000
--- a/v1.1.0/get-started/providers/Querying-for-proposers.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: 'Querying for Proposers'
-description: Use the pointers below to determine whether an upcoming proposer has opted in to mev-commit or not.
-sidebarTitle: Querying for Proposers
----
-
-## Querying for Proposers API
-
-Although querying for proposers may be more appropriate for bidders, provider nodes still have the ability to access this API.
-
-See [Querying for Proposers API](/v1.1.0/get-started/bidders/bidder-node-commands#querying-for-proposers-api) for more information.
diff --git a/v1.1.0/get-started/providers/sending-commitments.mdx b/v1.1.0/get-started/providers/sending-commitments.mdx
index e4ddfd15..06adce04 100644
--- a/v1.1.0/get-started/providers/sending-commitments.mdx
+++ b/v1.1.0/get-started/providers/sending-commitments.mdx
@@ -3,7 +3,7 @@ title: Sending Commitments
 sidebarTitle: Sending Commitments
 ---
 
-To send your first commitment, you will need to connect to the mev-commit Testnet. This will allow you to consume bids incoming to the network and submit commitments. To do this, you'll want to run an emulator to simulate accepting and rejecting bids. 
+To send your first commitment, you will need to connect to the mev-commit network. This will allow you to consume bids incoming to the network and submit commitments. To do this, you'll want to run an emulator to simulate accepting and rejecting bids. 
 
 
 <Tip>You will want to connect to a decisioning system that will accept and reject bids based on custom criteria. You can read more about the API to open a gRPC stream [here](/v1.1.0/api-reference/provider/sendprocessedbids).</Tip>
@@ -154,3 +154,7 @@ func ...() {
 </Step>
 </Steps>
 This should help you integrate bid processing into your system, allowing you to receive bid information and send back processed bids as commitments.
+
+## Querying for Proposers
+
+For advanced decision making, it may be relevant whether the next proposer is opted into mev-commit or not. Information on the opted in validators can be obtained via the [Querying for Proposers API](/v1.1.0/get-started/bidders/bidder-node-commands#querying-for-proposers-api).