describe the notifications api scopes

technoweenie · technoweenie · commit fcd6553fca7c · 2012-10-29T09:56:21.000-06:00
diff --git a/content/v3/activity/notifications.md b/content/v3/activity/notifications.md
@@ -23,10 +23,10 @@ user is involved including:
 * Commits the user authors or commits
 * Any discussion in which the user actively participates
 
-All Notification API calls require the <strong>"notifications"</strong> API
-scope.  Doing this will give read-only access to some Issue/Commit content.
-You will still need the "repo" scope to access Issues and Commits from their
-respective endpoints.
+All Notification API calls require the <strong>"notifications"</strong> or
+<strong>"repo</strong> API scopes.  Doing this will give read-only access to
+some Issue/Commit content. You will still need the "repo" scope to access
+Issues and Commits from their respective endpoints.
 
 Notifications come back as "threads".  A Thread contains information about the
 current discussion of an Issue/PullRequest/Commit.
diff --git a/content/v3/oauth.md b/content/v3/oauth.md
@@ -157,7 +157,7 @@ delete\_repo
 : Delete access to adminable repositories.
 
 notifications
-: Read access to a user's notifications.
+: Read access to a user's notifications.  `repo` is accepted too.
 
 gist
 : write access to gists.
