diff --git a/snaps/features/custom-ui/index.md b/snaps/features/custom-ui/index.md
index b4fb304aa46..7a8d6e38e82 100644
--- a/snaps/features/custom-ui/index.md
+++ b/snaps/features/custom-ui/index.md
@@ -857,7 +857,7 @@ The SVG is rendered within an `<img>` tag, which prevents JavaScript or interact
 being supported.
 
 :::note
-To disable image support, set the [`features.images`](../../reference/cli/options.md#featuresimages)
+To disable image support, set the [`features.images`](../../reference/config-options.md#featuresimages)
 configuration option to `false`.
 The default is `true`.
 :::
diff --git a/snaps/how-to/debug-a-snap/common-issues.md b/snaps/how-to/debug-a-snap/common-issues.md
index 5ba638bb920..5480ea25d25 100644
--- a/snaps/how-to/debug-a-snap/common-issues.md
+++ b/snaps/how-to/debug-a-snap/common-issues.md
@@ -18,10 +18,10 @@ If you encounter any issues that you can't solve on your own, please
 Because [Secure ECMAScript (SES)](../../learn/about-snaps/execution-environment.md) adds additional restrictions
 on the JavaScript runtime on top of strict mode, code that executes normally under strict mode might
 not under SES.
-[`yarn mm-snap build`](../../reference/cli/subcommands.md#b-build) by default attempts to execute a
+[`yarn mm-snap build`](../../reference/cli.md#b-build) by default attempts to execute a
 Snap in a stubbed SES environment.
 You can also disable this behavior and run the evaluation step separately using
-[`yarn mm-snap eval`](../../reference/cli/subcommands.md#e-eval).
+[`yarn mm-snap eval`](../../reference/cli.md#e-eval).
 If an error is thrown during this step, it's likely due to a SES incompatibility, and you must fix
 the issues manually.
 These incompatibilities tend to occur in dependencies.
diff --git a/snaps/how-to/test-a-snap.md b/snaps/how-to/test-a-snap.md
index 87aeee201a7..554bb089191 100644
--- a/snaps/how-to/test-a-snap.md
+++ b/snaps/how-to/test-a-snap.md
@@ -72,7 +72,7 @@ You can then run the `jest` command as usual.
 :::note
 `@metamask/snaps-jest` assumes the Snap is built in the directory you run Jest from.
 If you use a different directory, you can specify the path using the
-[`server.root`](../reference/cli/options.md#serverroot) option, or by running your own HTTP server.
+[`server.root`](../reference/config-options.md#serverroot) option, or by running your own HTTP server.
 It's currently not possible to use `@metamask/snaps-jest` with a Snap that is not built.
 :::
 
diff --git a/snaps/learn/about-snaps/execution-environment.md b/snaps/learn/about-snaps/execution-environment.md
index 782692a5641..a3eb2c90213 100644
--- a/snaps/learn/about-snaps/execution-environment.md
+++ b/snaps/learn/about-snaps/execution-environment.md
@@ -51,7 +51,7 @@ The following globals are also available:
 
 :::info note
 To use Node.js built-in modules such as `crypto` and `path`, set the
-[`polyfills`](../../reference/cli/options.md#polyfills) configuration option to `true`.
+[`polyfills`](../../reference/config-options.md#polyfills) configuration option to `true`.
 :::
 
 ## Secure ECMAScript (SES)
diff --git a/wallet/how-to/connect.md b/wallet/how-to/connect.md
index a3212ce201b..a0bf1f56566 100644
--- a/wallet/how-to/connect.md
+++ b/wallet/how-to/connect.md
@@ -445,6 +445,6 @@ You can clone the repository and run the example locally using `npm i && npm run
 After connecting to MetaMask directly, you can:
 
 - [Detect, add, and switch networks](/wallet/how-to/manage-networks).
-- [Send transactions](../how-to/send-transactions.md).
+- [Send transactions](../how-to/send-transactions/index.md).
 - [Sign data](../how-to/sign-data/index.md).
 - [Display tokens, contract methods, and icons in MetaMask](/wallet/how-to/display).