From 071c7416c84dfae9d81ab488523b47d5d3949b27 Mon Sep 17 00:00:00 2001 From: Maya Kaczorowski <15946341+mayakacz@users.noreply.github.com> Date: Thu, 19 Nov 2020 07:05:48 -0800 Subject: [PATCH] fix typo --- content/ui-patterns/feature-onboarding.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ui-patterns/feature-onboarding.mdx b/content/ui-patterns/feature-onboarding.mdx index 0c757e3..7b67695 100644 --- a/content/ui-patterns/feature-onboarding.mdx +++ b/content/ui-patterns/feature-onboarding.mdx @@ -33,7 +33,7 @@ When designing a feature onboarding flow, remember to: Create a new feature release timeline with clear parameters and an appropriate ramp down plan: - **Define why** - - System triggers, e.g. a new feature released, a user should not need to dismiss the same annoucement each time they visit a different repository. + - System triggers, e.g. a new feature released, a user should not need to dismiss the same announcement each time they visit a different repository. - User triggers, e.g. a user visits a specific repository for the first time, if recurring, a user should feel added value each time they see the message. - Consider how triggers may be tallied for users who belong to multiple repositories and organizations. - **Define when** -- GitLab