summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIlya Peterov <ipeterov1@gmail.com>2019-05-31 17:53:00 +0000
committerIlya Peterov <ipeterov1@gmail.com>2019-05-31 17:53:00 +0000
commit0f616b1d795dc7687710f01615e3e79226476e0c (patch)
treec9e98069dfb1925e989c688b5c3487d46c24ab03
parentb9798c157ac5973e9dd2b7ad95267014034a219f (diff)
downloadgitlab-ce-0f616b1d795dc7687710f01615e3e79226476e0c.tar.gz
Update 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.