Add latest changes from gitlab-org/gitlab@master

1 files changed, 14 insertions, 8 deletions

diff --git a/doc/development/documentation/alpha_beta.md b/doc/development/documentation/alpha_beta.md
index 4b5c24d512f..47f9090adbc 100644
--- a/doc/development/documentation/alpha_beta.md
+++ b/doc/development/documentation/alpha_beta.md
@@ -18,26 +18,32 @@ When you document a feature in one of these three statuses:
 These features are usually behind a feature flag, which follow [these documentation guidelines](feature_flags.md).
 
 If you add details of how users should enroll, or how to contact the team with issues,
-the `FLAG:` note should be above these details. For example:
+the `FLAG:` note should be above these details.
+
+For example:
 
 ```markdown
 ## Great new feature (Alpha)
 
+> [Introduced](link) in GitLab 15.10. This feature is in [Alpha](<link_to>/policy/alpha-beta-support.md).
+
 FLAG:
 On self-managed GitLab, by default this feature is not available.
-To make it available, ask an administrator to enable the feature flag named example_flag.
+To make it available, ask an administrator to enable the feature flag named `example_flag`.
 On GitLab.com, this feature is not available. This feature is not ready for production use.
 
 Use this great new feature when you need to do this new thing.
 
-This feature is in Alpha. To join the list of users testing this feature,
-do this thing. If you find a bug, [open an issue](link).
+This feature is in [Alpha](<link_to>/policy/alpha-beta-support.md). To join
+the list of users testing this feature, do this thing. If you find a bug,
+[open an issue](link).
 ```
 
-When the feature is released, remove:
+When the feature is ready for production, remove:
 
 - The text in parentheses.
-- Any language about the feature not being ready for production.
-- The feature flag information.
+- Any language about the feature not being ready for production in the body
+  description.
+- The feature flag information if available.
 
-Ensure the version history is up-to-date.
+Ensure the version history is up-to-date by adding a note about the production release.