Commit 1427a94f authored by Marcia Ramos's avatar Marcia Ramos

fix spelling

parent 3a0e9df6
...@@ -26,9 +26,9 @@ With [Multiple Issue Boards](#multiple-issue-boards), available only in [GitLab ...@@ -26,9 +26,9 @@ With [Multiple Issue Boards](#multiple-issue-boards), available only in [GitLab
Enterprise Edition](https://about.gitlab.com/gitlab-ee/), your workflow gets Enterprise Edition](https://about.gitlab.com/gitlab-ee/), your workflow gets
empowered with the ability to create multiple boards per project. empowered with the ability to create multiple boards per project.
## Use-cases ## Use cases
There are numerous use-cases for Issue Boards, we will just There are numerous use cases for Issue Boards, we will just
exemplify with a couple situations. exemplify with a couple situations.
For a broader use-case, please check the blog post For a broader use-case, please check the blog post
...@@ -65,7 +65,7 @@ members of their teams. We could have, therefore, three Issue Boards for this ca ...@@ -65,7 +65,7 @@ members of their teams. We could have, therefore, three Issue Boards for this ca
### Boards for Milestones ### Boards for Milestones
From the use-cases above, let's assume that you have now created a milestone per release for From the use cases above, let's assume that you have now created a milestone per release for
your app. You can create a milestone exclusive for each release, and [associate it with a board](#board-with-a-milestone). your app. You can create a milestone exclusive for each release, and [associate it with a board](#board-with-a-milestone).
Therefore, you'll have everything organized in a board per release. Therefore, you'll have everything organized in a board per release.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment