diff --git a/docs/resolvers/writing.mdx b/docs/resolvers/writing.mdx
index 5c4089f3..bd7f3573 100644
--- a/docs/resolvers/writing.mdx
+++ b/docs/resolvers/writing.mdx
@@ -12,11 +12,7 @@ export const meta = {
 Every ENS name has a resolver, which is responsible for resolving information about a name.
 By writing your own resolver contract you can extend the functionality of your name, subnames, and more.
 
-resolvers are a core part of the ENS protocol
-
-they give the power to a name "node" to control the resolution process from itself onwards (its subdomains etc)
-
-resolvers were originally standardized in EIP 137, but have since received a few updates such as [EIP 181](https://eips.ethereum.org/EIPS/eip-181), [EIP 2304](https://eips.ethereum.org/EIPS/eip-2304), and [ENSIP-10](/ensip/10).
+Resolvers are a core part of the ENS protocolm, they give the power to a name "node" to control the resolution process from itself onwards (its subdomains etc). Resolvers were originally standardized in EIP 137, but have since received a few updates such as [EIP 181](https://eips.ethereum.org/EIPS/eip-181), [EIP 2304](https://eips.ethereum.org/EIPS/eip-2304), and [ENSIP-10](/ensip/10).
 
 ## Resolver Interface