From c34263b655f946f194009aaa9571a4d9793ffe09 Mon Sep 17 00:00:00 2001
From: gregorydemay <112856886+gregorydemay@users.noreply.github.com>
Date: Wed, 23 Oct 2024 16:36:46 +0200
Subject: [PATCH] Improve docs

Co-authored-by: Jessie Mongeon <133128541+jessiemongeon1@users.noreply.github.com>
---
 .../multi-chain/ethereum/evm-rpc/how-it-works.mdx               | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/developer-docs/multi-chain/ethereum/evm-rpc/how-it-works.mdx b/docs/developer-docs/multi-chain/ethereum/evm-rpc/how-it-works.mdx
index 5b65eb6295..de1383d145 100644
--- a/docs/developer-docs/multi-chain/ethereum/evm-rpc/how-it-works.mdx
+++ b/docs/developer-docs/multi-chain/ethereum/evm-rpc/how-it-works.mdx
@@ -24,7 +24,7 @@ By default for Candid-RPC methods such as `eth_getTransactionReceipt`, the EVM R
 
 ## Authentication
 
-Certain JSON-RPC endpoints require an API key to authenticate with the RPC provider. The EVM RPC canister is configured with the required API keys to that a developer does not need to deal with them. A developer can still choose to use custom providers (with or without API keys) to make the call instead if desired. API keys typically have a subscription fee associated with them, but developers who use the EVM RPC canister's pre-configured keys do not need to subscribe to the RPC services themselves.
+Certain JSON-RPC endpoints require an API key to authenticate with the RPC provider. The EVM RPC canister is already configured with the required API keys, although a developer can still choose to use custom providers (with or without API keys) to make the call instead if desired. API keys typically have a subscription fee associated with them, but developers who use the EVM RPC canister's pre-configured keys do not need to subscribe to the RPC services themselves.
 
 When not using API keys, developers should be mindful of: