From 317a204070f5722c54e668c2d52631f9356320fb Mon Sep 17 00:00:00 2001 From: Michael Ferranti Date: Tue, 2 Apr 2024 11:44:23 +0200 Subject: [PATCH] fixed typo (#6694) found a small typo and fixed it. --- website/docs/reference/feature-flag-naming-patterns.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/feature-flag-naming-patterns.mdx b/website/docs/reference/feature-flag-naming-patterns.mdx index 8bbac40c8d6..993a68299c5 100644 --- a/website/docs/reference/feature-flag-naming-patterns.mdx +++ b/website/docs/reference/feature-flag-naming-patterns.mdx @@ -16,7 +16,7 @@ Patterns are implicitly anchored to the start and end of the string. This means Feature flag naming patterns are defined on a per-project basis. -In addition to the pattern itself, you can also define a an example and a description of the pattern. If defined, both the example and the description will be shown to the user when they are creating a new feature flag. +In addition to the pattern itself, you can also define an example and a description of the pattern. If defined, both the example and the description will be shown to the user when they are creating a new feature flag. ## Overview