diff --git a/website/src/app/kb/deploy/clients/readme.mdx b/website/src/app/kb/deploy/clients/readme.mdx
index 465f5316e..b9fac4a66 100644
--- a/website/src/app/kb/deploy/clients/readme.mdx
+++ b/website/src/app/kb/deploy/clients/readme.mdx
@@ -95,9 +95,9 @@ platform-specific notes, use the following details:
 
 macOS configurations are applied as `.mobileconfig` provisioning profiles, which
 can be created by popular profile creator tools, such as
-[Apple Configurator](https://support.apple.com/guide/apple-configurator/welcome/mac)
-or [iMazing Profile Editor](https://imazing.com/profile-editor). We recommend
-using iMazing Profile Editor as it has built-in support for generating Firezone
+[Apple Configurator](https://support.apple.com/apple-configurator) or
+[iMazing Profile Editor](https://imazing.com/profile-editor). We recommend using
+iMazing Profile Editor as it has built-in support for generating Firezone
 profiles.
 
 If you'd prefer to create the file manually, you can
diff --git a/website/src/app/kb/reference/faq/readme.mdx b/website/src/app/kb/reference/faq/readme.mdx
index e13b79868..8527e6ae6 100644
--- a/website/src/app/kb/reference/faq/readme.mdx
+++ b/website/src/app/kb/reference/faq/readme.mdx
@@ -131,8 +131,8 @@ traffic.
 
 Scaling Firezone to support your rapidly growing organization is as simple as
 deploying additional Gateway servers. See our
-[Terraform deployment examples](/kb/automate/terraform) for an idea of how to
-automate this process.
+[Terraform deployment examples](/kb/automate) for an idea of how to automate
+this process.
 
 #### What protocol does Firezone use to encrypt traffic?