Merge branch 'notifications-title' into 'master'

fixed notifications title I fixed the title and link to this document because I believe that it's more clear and easier to find if it has "emails" in the name. See merge request !1897

Merge branch 'notifications-title' into 'master'
1da6d42b · Job van der Voort · 070d6a24 · 3d6e67e4 · 1da6d42b · 1da6d42b
Commit 1da6d42b authored Jul 14, 2015 by Job van der Voort
Hide whitespace changes
Inline Side-by-side

Showing with 3 additions and 5 deletions

README.md doc/workflow/README.md +1 -1

notifications.md doc/workflow/notifications.md +2 -4

No files found.
--- a/doc/workflow/README.md
+++ b/doc/workflow/README.md
@@ -7,7 +7,7 @@
 - [Groups](groups.md)
 - [Keyboard shortcuts](shortcuts.md)
 - [Labels](labels.md)
- [Notifications](notifications.md)
+- [Notification emails](notifications.md)
 - [Project Features](project_features.md)
 - [Project forking workflow](forking_workflow.md)
 - [Protected branches](protected_branches.md)

--- a/doc/workflow/notifications.md
+++ b/doc/workflow/notifications.md
-# GitLab Notifications
+# GitLab Notification Emails

-GitLab has notifications system in place to notify a user of events important for the workflow.
+GitLab has a notification system in place to notify a user of events that are important for the workflow.

 ## Notification settings

@@ -67,5 +67,3 @@ Below is the table of events users can be notified of:
 | Reopen merge request         | Project members [1]                                               | [1] higher than participating |
 | Merge merge request          | MR author [1], MR assignee [2], project members [3]               | [1] [2] not disabled, [3] higher than participating |
 | New comment                  | Mentioned users [1], users participating [2], project members [3] | [1] [2] not disabled, [3] higher than participating |
-
-