diff --git a/doc/development/code_suggestions/index.md b/doc/development/code_suggestions/index.md
index 4098e4f6512c0e4d37bbfd480823e0727af6c32d..d07069386ef6a510fc98c0711dc031cd140a8f3d 100644
--- a/doc/development/code_suggestions/index.md
+++ b/doc/development/code_suggestions/index.md
@@ -42,7 +42,7 @@ This should enable everyone to see locally any change in an IDE being sent to th
 When testing interactions with the AI Gateway, you might want to integrate your local GDK
 with the deployed staging AI Gateway. To do this:
 
-1. You need a [cloud staging license](../../user/project/repository/code_suggestions/self_managed_prior_versions.md#upgrade-to-gitlab-163) that has the Code Suggestions add-on, because add-ons are enabled on staging. Drop a note in the `#s_fulfillment` internal Slack channel to request an add-on to your license. See this [handbook page](https://about.gitlab.com/handbook/developer-onboarding/#working-on-gitlab-ee-developer-licenses) for how to request a license for local development.
+1. You need a [cloud staging license](../../user/project/repository/code_suggestions/self_managed_prior_versions.md#upgrade-to-gitlab-163) that has the Code Suggestions add-on, because add-ons are enabled on staging. Drop a note in the `#s_fulfillment` internal Slack channel to request an add-on to your license. See this [handbook page](https://handbook.gitlab.com/handbook/developer-onboarding/#working-on-gitlab-ee-developer-licenses) for how to request a license for local development.
 1. Set environment variables to point customers-dot to staging, and the AI Gateway to staging:
 
    ```shell