diff --git a/apps/base-docs/docs/pages/cookbook/client-side-development/introduction-to-providers.mdx b/apps/base-docs/docs/pages/cookbook/client-side-development/introduction-to-providers.mdx
index 5035696add..76f9443d71 100644
--- a/apps/base-docs/docs/pages/cookbook/client-side-development/introduction-to-providers.mdx
+++ b/apps/base-docs/docs/pages/cookbook/client-side-development/introduction-to-providers.mdx
@@ -52,7 +52,7 @@ You'll encounter providers divided into three general categories: Public Provide
 
 Many tutorials and guides, including the getting started guide for [wagmi], use a _Public Provider_ as the default to get you up and running. Public means that they're open, permissionless, and free, so the guides will also usually warn you that you need to add another provider if you don't want to run into rate limiting. Listen to these warnings! The rate-limits of public providers are severe, and you'll start getting limited very quickly.
 
-In wagmi, a public client is automatically included in the default confit. This client is just a wrapper setting up a [JSON RPC] provider using the `chain` and `rpcUrls` listed in Viem's directory of chain information. You can view the [data for Base Sepolia here].
+In wagmi, a public client is automatically included in the default config. This client is just a wrapper setting up a [JSON RPC] provider using the `chain` and `rpcUrls` listed in Viem's directory of chain information. You can view the [data for Base Sepolia here].
 
 Most chains will list this information in their docs as well. For example, on the network information pages for [Base] and [Optimism]. If you wanted, you could manually set up a `jsonRpcProvider` in wagmi using this information.