Update accounts.mdx

Author: evanorti

sdk/next/learn/concepts/accounts.mdx

@@ -110,7 +110,7 @@ Cosmos SDK supports several account types that extend the base account model:
 
 - **Base account**: A standard account that holds balances and signs transactions. This is the most common account type for users.
 
-- **Module account**: Owned by a [module](/sdk/next/learn/concepts/modules) rather than a user. Module accounts are derived from the module name and cannot be controlled by a private key. For example, the staking module uses a module account to hold all delegated tokens, and the distribution module uses a module account to hold rewards before they are distributed. This design allows protocol logic to custody tokens without requiring a private key holder, which is essential for decentralized operations. For a worked example of adding a module account to receive fees, see [Module accounts](/sdk/next/tutorials/example/04-counter-walkthrough#module-accounts) in the Full Counter Module Walkthrough.
+- **Module account**: Owned by a [module](/sdk/next/learn/concepts/modules) rather than a user. Module accounts are derived from the module name and cannot be controlled by a private key. For example, the staking module uses a module account to hold all delegated tokens, and the distribution module uses a module account to hold rewards before they are distributed. This design allows protocol logic to custody tokens without requiring a private key holder, which is essential for decentralized operations. For a working example of adding a module account to receive fees, see [Module accounts](/sdk/next/tutorials/example/04-counter-walkthrough#module-accounts) in the Full Counter Module Walkthrough.
 
 - **Vesting account**: Holds tokens that unlock gradually over time according to a schedule. Vesting accounts are often used for team allocations or investor tokens that vest over months or years. They restrict spending to only unlocked tokens while still allowing the account to participate in staking and governance.