diff --git a/develop-docs/backend/application-domains/feature-flags/flagpole.mdx b/develop-docs/backend/application-domains/feature-flags/flagpole.mdx
index cfb9700a86238..1b081fc74c70e 100644
--- a/develop-docs/backend/application-domains/feature-flags/flagpole.mdx
+++ b/develop-docs/backend/application-domains/feature-flags/flagpole.mdx
@@ -228,7 +228,7 @@ options:
       rollout: 100
 ```
 
-You can push your feature option to your local devserver using the following `getsentry` CLI command:
+You can push your feature option to your local devserver using the following `getsentry configoptions` CLI command:
 
 ```bash
 getsentry configoptions -f <path>/<to>/<your>/<config>.yml -l DEBUG patch
@@ -240,3 +240,10 @@ you remove the feature option.
 
 To unset your feature, comment out or remove your feature config from the
 `option` object, and rerun the `getsentry configoptions` command above.
+
+## Removing Flagpole features
+
+Because our options automator CI relies on the feature definitions in both Sentry and GetSentry, flags must be removed in a specific order to avoid causing test failures:
+1. Remove all flag checks from the codebase and set a default value of `True` for the flag.
+2. Once all flag checks have been removed and the changes have been deployed to all environments, remove the feature flag config from options automator.
+3. Remove the [feature registration](#rolling-out-a-new-flagpole-feature) from GetSentry or Sentry.