Merge pull request #25 from OpenZeppelin/chore/white-glove

chore/white glove

Author: stevedylandev

content/community-contracts/account-modules.mdx

@@ -10,12 +10,12 @@ ERC-7579 defines a standardized interface for modular smart accounts. This stand
 
 ### Accounts
 
-OpenZeppelin offers an implementation of an [`AccountERC7579`](contracts/v5.x/api/account.mdx#AccountERC7579) contract that allows installing modules compliant with this standard. There’s also an [`AccountERC7579Hooked`](contracts/v5.x/api/account.mdx#AccountERC7579Hooked) variant that supports installation of hooks. Like [most accounts](accounts.mdx#handling_initialization), an instance should define an initializer function where the first module that controls the account will be set:
+OpenZeppelin offers an implementation of an [`AccountERC7579`](/community-contracts/api/account#AccountERC7579) contract that allows installing modules compliant with this standard. There’s also an [`AccountERC7579Hooked`](/community-contracts/api/account#AccountERC7579Hooked) variant that supports installation of hooks. Like [most accounts](accounts#handling_initialization), an instance should define an initializer function where the first module that controls the account will be set:
 
 <include cwd lang='solidity'>./examples/account/MyAccountERC7579.sol</include>
 
 <Callout>
-For simplicity, the [`AccountERC7579Hooked`](contracts/v5.x/api/account.mdx#AccountERC7579Hooked) only supports a single hook. A common workaround is to install a [single hook with a multiplexer pattern](https://github.com/rhinestonewtf/core-modules/blob/7afffccb44d73dbaca2481e7b92bce0621ea6449/src/HookMultiPlexer/HookMultiPlexer.sol) to extend the functionality to multiple hooks.
+For simplicity, the [`AccountERC7579Hooked`](/community-contracts/api/account#AccountERC7579Hooked) only supports a single hook. A common workaround is to install a [single hook with a multiplexer pattern](https://github.com/rhinestonewtf/core-modules/blob/7afffccb44d73dbaca2481e7b92bce0621ea6449/src/HookMultiPlexer/HookMultiPlexer.sol) to extend the functionality to multiple hooks.
 </Callout>
 
 ### Modules
@@ -35,12 +35,12 @@ See [popular module implementations](https://erc7579.com/modules).
 
 The library provides _standard composable modules_ as building blocks with an internal API for developers. By combining these components, you can create a rich set of variants without including unnecessary features.
 
-A good starting point is the [`ERC7579Executor`](contracts/v5.x/api/account.mdx#ERC7579Executor) or [`ERC7579Validator`](contracts/v5.x/api/account.mdx#ERC7579Validator), which include an opinionated base layer easily combined with other abstract modules. Hooks and fallback handlers are more straightforward to implement directly from interfaces:
+A good starting point is the [`ERC7579Executor`](/community-contracts/api/account#ERC7579Executor) or [`ERC7579Validator`](/community-contracts/api/account#ERC7579Validator), which include an opinionated base layer easily combined with other abstract modules. Hooks and fallback handlers are more straightforward to implement directly from interfaces:
 
 <include cwd lang='solidity'>./examples/account/modules/MyERC7579Modules.sol</include>
 
 <Callout>
-Explore these abstract ERC-7579 modules in the [API Reference](contracts/v5.x/api/account.mdx#modules).
+Explore these abstract ERC-7579 modules in the [API Reference](/community-contracts/api/account#modules).
 </Callout>
 
 #### Execution Modes
@@ -97,24 +97,24 @@ Social recovery is not a single solution but a design space with multiple config
 * Cancellation windows
 * Confirmation requirements
 
-To support _different guardian types_, we can leverage ERC-7913 as discussed in the [multisig](multisig.mdx#beyond_standard_signature_verification) section. For ERC-7579 modules, this is implemented through the [`ERC7579Multisig`](contracts/v5.x/api/account.mdx#ERC7579Multisig) validator.
+To support _different guardian types_, we can leverage ERC-7913 as discussed in the [multisig](multisig#beyond_standard_signature_verification) section. For ERC-7579 modules, this is implemented through the [`ERC7579Multisig`](/community-contracts/api/account#ERC7579Multisig) validator.
 
-Combined with an [`ERC7579Executor`](contracts/v5.x/api/account.mdx#ERC7579Executor), it provides a basic foundation that can be extended with more sophisticated features:
+Combined with an [`ERC7579Executor`](/community-contracts/api/account#ERC7579Executor), it provides a basic foundation that can be extended with more sophisticated features:
 
 <include cwd lang='solidity'>./examples/account/modules/MyERC7579SocialRecovery.sol</include>
 
-For enhanced security, you can extend this foundation with scheduling, delays, and cancellations using [`ERC7579DelayedExecutor`](contracts/v5.x/api/account.mdx#ERC7579DelayedExecutor). This allows guardians to schedule recovery operations with a time delay, providing a security window to detect and cancel suspicious recovery attempts before they execute:
+For enhanced security, you can extend this foundation with scheduling, delays, and cancellations using [`ERC7579DelayedExecutor`](/community-contracts/api/account#ERC7579DelayedExecutor). This allows guardians to schedule recovery operations with a time delay, providing a security window to detect and cancel suspicious recovery attempts before they execute:
 
 <include cwd lang='solidity'>./examples/account/modules/MyERC7579DelayedSocialRecovery.sol</include>
 
 <Callout>
-The delayed executor’s signature validation doesn’t require a nonce since operations are uniquely identified by their [operation id](contracts/v5.x/api/account.mdx#ERC7579DelayedExecutor-hashOperation-address-bytes32-bytes32-bytes-) and cannot be scheduled twice.
+The delayed executor’s signature validation doesn’t require a nonce since operations are uniquely identified by their [operation id](/community-contracts/api/account#ERC7579DelayedExecutor-hashOperation-address-bytes32-bytes32-bytes-) and cannot be scheduled twice.
 </Callout>
 
 These implementations demonstrate how to build progressively more secure social recovery mechanisms, from basic multi-signature recovery to time-delayed recovery with cancellation capabilities.
 
 For additional functionality, developers can use:
 
-* [`ERC7579MultisigWeighted`](contracts/v5.x/api/account.mdx#ERC7579MultisigWeighted) to assign different weights to signers
-* [`ERC7579MultisigConfirmation`](contracts/v5.x/api/account.mdx#ERC7579MultisigConfirmation) to implement a confirmation system that verifies signatures when adding signers
-* [`ERC7579MultisigStorage`](contracts/v5.x/api/account.mdx#ERC7579MultisigStorage) to allow guardians to presign recovery operations for more flexible coordination
+* [`ERC7579MultisigWeighted`](/community-contracts/api/account#ERC7579MultisigWeighted) to assign different weights to signers
+* [`ERC7579MultisigConfirmation`](/community-contracts/api/account#ERC7579MultisigConfirmation) to implement a confirmation system that verifies signatures when adding signers
+* [`ERC7579MultisigStorage`](/community-contracts/api/account#ERC7579MultisigStorage) to allow guardians to presign recovery operations for more flexible coordination