diff --git a/docs/developer/release-process.md b/docs/developer/release-process.md
index 01f2c9cca3..ea961b93b7 100644
--- a/docs/developer/release-process.md
+++ b/docs/developer/release-process.md
@@ -59,7 +59,7 @@ branch docs PR. Specifically:
       4. `VERSION` in top-level Makefile.
       5. Any references in the docs to the previous release.
       6. Any installation instructions to ensure that the supported Gateway API and NGF versions are correct.Specifically, helm README and `site/content/includes/installation/install-gateway-api-resources.md`.
-11. Update the production branch to the latest release branch in [Netlify](https://app.netlify.com/sites/nginx-gateway-fabric/configuration/deploys#branches-and-deploy-contexts). If it's your first time, log in using Gitlab SSO and ask the docs team for permission to access the NGF project. Once the branch is updated, redeploy the docs in Netlify. Verify that the Netlify deploy passes and that the published docs look good (no obvious errors or issues).
+11. Ask the docs team to update the production branch for NGF in Netlify to our latest release branch and run the deployment pipeline.
 12. Close the issue created in Step 1.
 13. Ensure that the [associated milestone](https://github.com/nginxinc/nginx-gateway-fabric/milestones) is closed.
 14. Verify that published artifacts in the release can be installed properly.