diff --git a/src/docs/feature-flags/index.mdx b/src/docs/feature-flags/index.mdx
index 52186d2646..a0b4d36159 100644
--- a/src/docs/feature-flags/index.mdx
+++ b/src/docs/feature-flags/index.mdx
@@ -187,6 +187,7 @@ Feature flags are declared in Sentry's codebase. For self-hosted users, those
 flags are then configured via `sentry.conf.py`. For Sentry's SaaS deployment,
 you have the choice of using an option backed rollout via Options Automator with Flagpole,
 or by writing a custom feature flag handler.
+
 - [Flagpole](/feature-flags/flagpole/) is Sentry's internal feature flagging library, allowing a feature
 with multiple target segments and condition filters to be defined in YAML within Options Automator.
 
@@ -204,8 +205,8 @@ sentry.io, you have a few potential paths:
 - If the feature cannot be disabled, or you don't need to conditionally disable
   the feature, remove the feature flag and all related checks from the Sentry
   code base. If necessary, also remove references to the feature from the
-  [self-hosted](https://github.com/getsentry/self-hosted) and getsentry
-  repositories.
+  [self-hosted](https://github.com/getsentry/self-hosted), getsentry, and
+  options-automator repositories.
 - If the feature will only be available to SaaS customers on specific plans, you
   need to add your feature flag to the appropriate plans and update feature
   handlers (see below).You should also enable the feature by default in
@@ -233,4 +234,4 @@ implement a feature handler in getsentry. For example, you can create a feature
 
 1. Disable the feature in `getsentry/conf/settings/defaults.py` by updating `SENTRY_FEATURES`.
 2. Add a new feature handler class in `getsentry/features.py` that determines availability of the feature based on the organization or actor.
-3. Register the handler at the bottom of `getsentry/features.py`.
\ No newline at end of file
+3. Register the handler at the bottom of `getsentry/features.py`.