diff --git a/docs/docs/api/cronjob.md b/docs/docs/api/cronjob.md
index 2dcb87de..921ef681 100644
--- a/docs/docs/api/cronjob.md
+++ b/docs/docs/api/cronjob.md
@@ -27,7 +27,7 @@ This creates a new CronJob, which will immediately be picked up by your local Qu
 
 :::note
 During development, your local Quirrel instance is able to detect `CronJob()` calls by watching your source directory.
-To register cron jobs on deployment, run `quirrel ci` [during deployment](/deploying)
+To register cron jobs on deployment, run `quirrel ci` [during deployment](/deployment/connecting)
 :::
 
 :::note
diff --git a/docs/docs/migrating-servers.md b/docs/docs/migrating-servers.md
index 20155cd9..b5b17eac 100644
--- a/docs/docs/migrating-servers.md
+++ b/docs/docs/migrating-servers.md
@@ -18,7 +18,7 @@ If that's a problem for your application, [get in touch](mailto:migration@quirre
 Here's the step-by-step guide:
 
 1. Upgrade your application to Quirrel v1.9.1
-2. Deploy your own Instance by following [https://github.com/quirrel-dev/quirrel-on-railway](https://github.com/quirrel-dev/quirrel-on-railway) or [https://docs.quirrel.dev/deploying](https://docs.quirrel.dev/deploying). Note down the access token.
+2. Deploy your own Instance by following [https://github.com/quirrel-dev/quirrel-on-railway](https://github.com/quirrel-dev/quirrel-on-railway) or [https://docs.quirrel.dev/deployment/connecting](https://docs.quirrel.dev/deployment/connecting). Note down the access token.
 3. Make the following changes to your application's environment variables:
     - set `QUIRREL_MIGRATE_OLD_API_URL` to the hostname of your old instance. If you used hosted Quirrel, that's `api.quirrel.dev`.
     - set `QUIRREL_MIGRATE_OLD_TOKEN` to the token that previously was set for `QUIRREL_TOKEN`
diff --git a/docs/docs/netlify-acquisition-faq.md b/docs/docs/netlify-acquisition-faq.md
index bfa733ae..aa2b4169 100644
--- a/docs/docs/netlify-acquisition-faq.md
+++ b/docs/docs/netlify-acquisition-faq.md
@@ -20,7 +20,7 @@ You're invited to try Netlify’s latest Scheduled Functions release in Netlify
 If you’re already hosting your site on Netlify, it’s [as easy as adding a few lines to your existing functions or `netlify.toml`](https://ntl.fyi/sched-func).
 And if you haven’t had a chance to use Netlify yet, even if you’re hosting your website somewhere else, Netlify Functions is a fantastic way to host (and now schedule!) your serverless functions.
 
-If you’re using some of Quirrel’s more advanced features that we don’t yet support on Netlify, you may also choose to [deploy Quirrel in your own infrastructure](https://docs.quirrel.dev/deploying#how-to-deploy-your-own-server), or use a service like [Zeplo](https://www.zeplo.io).
+If you’re using some of Quirrel’s more advanced features that we don’t yet support on Netlify, you may also choose to [deploy Quirrel in your own infrastructure](https://docs.quirrel.dev/deployment/connecting), or use a service like [Zeplo](https://www.zeplo.io).
 
 ## I have more questions! How can I get in touch?
 
diff --git a/docs/docusaurus.config.js b/docs/docusaurus.config.js
index 725adc5e..10a8102d 100644
--- a/docs/docusaurus.config.js
+++ b/docs/docusaurus.config.js
@@ -90,7 +90,7 @@ module.exports = {
             },
             {
               label: "Deploy",
-              to: "/deploying",
+              to: "/deployment/connecting",
             },
           ],
         },