summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMarcia Ramos <virtua.creative@gmail.com>2017-06-29 11:16:03 -0300
committerMarcia Ramos <virtua.creative@gmail.com>2017-06-29 11:16:03 -0300
commit93bf4263b99b9c6ccb1d3a75b052f16939ed91db (patch)
tree9f4818b0ca59c53de55bb5f63c555a0fe56e4094 /doc
parent025aca03d23b3f6c6aca65b2c923adc022d6e942 (diff)
downloadgitlab-ce-93bf4263b99b9c6ccb1d3a75b052f16939ed91db.tar.gz
Axil's review
Diffstat (limited to 'doc')
-rw-r--r--doc/user/project/issue_board.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md
index 6ae9fd57ad4..439b9a9fcc6 100644
--- a/doc/user/project/issue_board.md
+++ b/doc/user/project/issue_board.md
@@ -24,11 +24,11 @@ issue tracker.
## Use-cases
-There are numerous use-cases for the use of Issue Boards, we will just
-exemplify with a couple situations, but the possibilities go where our creativity goes.
+There are numerous use-cases for Issue Boards, we will just
+exemplify with a couple situations.
GitLab Workflow allows you to discuss proposals in issues, categorize them
-with labels, and and from there organize and prioritize them with Issue Boards.
+with labels, and from there organize and prioritize them with Issue Boards.
- For example, let's consider this simplified development workflow:
you have a repository hosting your app's codebase