diff --git a/docs/cloud/resources/best-practices.md b/docs/cloud/resources/best-practices.md
index bbc9e12b..da77af8e 100644
--- a/docs/cloud/resources/best-practices.md
+++ b/docs/cloud/resources/best-practices.md
@@ -30,6 +30,6 @@ Batch handler data filtering used to be compulsory before the release of `@subsq
   1. Deploy your squid to a [Professional organization](/cloud/resources/organizations/#professional-organizations).
   2. Use [`dedicated: true`](/cloud/reference/scale/#dedicated) in the `scale:` section of the manifest.
   3. Make sure that your [`scale:` section](/cloud/reference/scale) requests a sufficient but not excessive amount of resources.
-  4. Set your deployment up for [zero downtime updates](/cloud/resources/slots-and-tags/#zero-downtime-updates). Use a tag-based URL and and not slot-based URLs to access your API e.g. from your frontend app.
+  4. Set your deployment up for [zero downtime updates](/cloud/resources/slots-and-tags/#zero-downtime-updates). Use a tag-based URL and not slot-based URLs to access your API e.g. from your frontend app.
   5. Make sure to use [secrets](/cloud/resources/env-variables/#secrets) for all sensitive data you might've used in your code. The most common type of such data is API keys and URLs containing them.
   6. Follow the recommendations from the [Cloud logging page](/cloud/resources/logging).
diff --git a/docs/cloud/resources/rpc-proxy.md b/docs/cloud/resources/rpc-proxy.md
index fbdcc89c..694ee1d3 100644
--- a/docs/cloud/resources/rpc-proxy.md
+++ b/docs/cloud/resources/rpc-proxy.md
@@ -59,7 +59,7 @@ Among other things, this enables a development process that uses the service for
    This will add and populate the `RPC_ETH_HTTP` variable for Cloud deployments.
 
 
-3. Configure the processor to use the URL from from `RPC_ETH_HTTP`:
+3. Configure the processor to use the URL from `RPC_ETH_HTTP`:
    ```ts
    import {EvmBatchProcessor} from '@subsquid/evm-processor'
    import {assertNotNull} from '@subsquid/util-internal'