Apply suggestions from code review

Co-authored-by: Jun Lee <[email protected]>

Author: dario-piotrowicz

src/content/docs/workers/development-testing/index.mdx

@@ -295,7 +295,7 @@ Certain bindings are not supported for remote connections during local developme
 
 If `experimental_remote: true` is specified in Wrangler configuration for any of the following unsupported binding types, Cloudflare **will issue an error**. See [all supported and unsupported bindings for remote bindings](/workers/development-testing/bindings-per-env/).
 
-- [**Durable Objects**](/workers/wrangler/configuration/#durable-objects): Enabling remote connections for Durable Objects may be supported in the future, but currently will always run locally. However, using Durable Objects in combination with remote bindings is possible as illustrated in the [Durable Objects usage section](#durable-objects-usage-with-remote-resources) below.
+- [**Durable Objects**](/workers/wrangler/configuration/#durable-objects): Enabling remote connections for Durable Objects may be supported in the future, but currently will always run locally. However, using Durable Objects in combination with remote bindings is possible, as illustrated in the [Durable Objects usage section](#durable-objects-usage-with-remote-resources) below.
 
 - [**RPC on service bindings**](/workers/runtime-apis/bindings/service-bindings/rpc/): While you can make `fetch()` calls on remote service bindings, you cannot currently call RPC methods on remote service bindings.
 
@@ -327,13 +327,12 @@ There are two recommended patterns for this:
 
 - **Local Durable Objects/Workflows with remote bindings:**
 
-	When you enable remote bindings in your [Wrangler configuration](/workers/wrangler/configuration), your locally running Durable Objects and Workflows can access those remote resources.
-	This allows such bindings, although run locally to interact with remote resources during local development.
+	When you enable remote bindings in your [Wrangler configuration](/workers/wrangler/configuration), your locally running Durable Objects and Workflows can access remote resources. This allows such bindings, although run locally, to interact with remote resources during local development.
 
 - **Accessing remote Durable Objects/Workflows via service bindings:**
 
 	To interact with remote Durable Object or Workflow instances, deploy a Worker that defines those. Then, in your local Worker, configure a remote [service binding](/workers/runtime-apis/bindings/service-bindings/) pointing to the deployed Worker.
-	Your local Worker will be then able to interact with the remote deployed Worker which in turn can communicate with the remote Durable Objects/Workflows. In such a manner you can create a communication channel via the remote service binding, effectively using the deployed Worker as a proxy interface to the remote bindings during local development.
+	Your local Worker will be then able to interact with the remote deployed Worker, which in turn can communicate with the remote Durable Objects/Workflows. Using this method, you can create a communication channel via the remote service binding, effectively using the deployed Worker as a proxy interface to the remote bindings during local development.
 
 
 ### Important Considerations