Commit a82596e9 authored by Amy Qualls's avatar Amy Qualls

Merge branch 'msj-flag-doc' into 'master'

Fix inconsistencies in feature flag examples

See merge request gitlab-org/gitlab!75043
parents a02124bc 17882e0c
...@@ -58,7 +58,7 @@ FLAG: ...@@ -58,7 +58,7 @@ FLAG:
If needed, you can add this sentence: If needed, you can add this sentence:
`You should not use this feature for production environments.` `The feature is not ready for production use.`
## Add version history text ## Add version history text
...@@ -109,7 +109,7 @@ And, when the feature is done and fully available to all users: ...@@ -109,7 +109,7 @@ And, when the feature is done and fully available to all users:
```markdown ```markdown
> - Introduced in GitLab 13.7 [with a flag](../../administration/feature_flags.md) named `forti_token_cloud`. Disabled by default. > - Introduced in GitLab 13.7 [with a flag](../../administration/feature_flags.md) named `forti_token_cloud`. Disabled by default.
> - [Enabled on self-managed](https://gitlab.com/issue/etc) GitLab 13.8. > - [Enabled on self-managed](https://gitlab.com/issue/etc) in GitLab 13.8.
> - [Enabled on GitLab.com](https://gitlab.com/issue/etc) in GitLab 13.9. > - [Enabled on GitLab.com](https://gitlab.com/issue/etc) in GitLab 13.9.
> - [Generally available](issue-link) in GitLab 14.0. [Feature flag <flag name>](issue-link) removed. > - [Generally available](issue-link) in GitLab 14.0. [Feature flag <flag name>](issue-link) removed.
``` ```
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment