summaryrefslogtreecommitdiff
path: root/doc/user/project/issues/multiple_assignees_for_issues.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/project/issues/multiple_assignees_for_issues.md')
-rw-r--r--doc/user/project/issues/multiple_assignees_for_issues.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/project/issues/multiple_assignees_for_issues.md b/doc/user/project/issues/multiple_assignees_for_issues.md
index 8781ebdd5b0..d1db0790d69 100644
--- a/doc/user/project/issues/multiple_assignees_for_issues.md
+++ b/doc/user/project/issues/multiple_assignees_for_issues.md
@@ -22,7 +22,7 @@ Consider a team formed by frontend developers, backend developers,
UX designers, QA testers, and a product manager working together to bring an idea to
market.
-Multiple Assignees for Issues makes collaboration smother,
+Multiple Assignees for Issues makes collaboration smoother,
and allows shared responsibilities to be clearly displayed.
All assignees are shown across your team's workflows and receive notifications (as they
would as single assignees), simplifying communication and ownership.