summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJason Lenny <jlenny@gitlab.com>2019-01-03 15:19:18 +0000
committerJason Lenny <jlenny@gitlab.com>2019-01-03 15:19:18 +0000
commit025bf68c2cfc9a28df87cf569b9e3e9ad5805e9c (patch)
tree2bbf0208b641e0067953730b268f5d5c69610c06
parent5054a8cdd3e519aea9a3195175d9dd695dd85399 (diff)
downloadgitlab-ce-025bf68c2cfc9a28df87cf569b9e3e9ad5805e9c.tar.gz
Don't call release notes releases
-rw-r--r--doc/workflow/releases.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/workflow/releases.md b/doc/workflow/releases.md
index 2808fd36d34..02388bb73ea 100644
--- a/doc/workflow/releases.md
+++ b/doc/workflow/releases.md
@@ -2,7 +2,7 @@
NOTE: In GitLab 11.7, we introduced the full fledged [releases](../user/project/releases.md) feature. You can still create release notes on this page, but the new method is preferred.
-You can turn any git tag into a release by adding a note to it. Release notes
+You can add release notes to any git tag using the notes feature. Release notes
behave like any other markdown form in GitLab so you can write text and
drag-n-drop files to it. Release notes are stored in GitLab's database.