Remove misleading parameters in notifications API

jasonrudolph · jasonrudolph · commit 34a7456b687c · 2013-03-29T09:58:00.000-04:00
The API allows you to mark notifications as read. To do so, you can
specify any one of the following parameters and values.

  - "unread" : false
  - "read" : true
  - none of the above

In all cases, the result is the same: it marks the notifications as
read. Therefore, passing neither is the simplest approach, and there is
no reason to describe these parameters.
diff --git a/content/v3/activity/notifications.md b/content/v3/activity/notifications.md
@@ -108,12 +108,6 @@ on GitHub.com](https://github.com/notifications).
 
 ### Input
 
-unread
-: **Boolean** Changes the unread status of the threads.
-
-read
-: **Boolean** Inverse of "unread".
-
 last_read_at
 : _Optional_ **Time** Describes the last point that notifications were checked.  Anything
 updated since this time will not be updated.  Default: Now.  Expected in ISO
@@ -132,12 +126,6 @@ from the [default view on GitHub.com](https://github.com/notifications).
 
 ### Input
 
-unread
-: **Boolean** Changes the unread status of the threads.
-
-read
-: **Boolean** Inverse of "unread".
-
 last_read_at
 : _Optional_ **Time** Describes the last point that notifications were checked.  Anything
 updated since this time will not be updated.  Default: Now.  Expected in ISO
@@ -160,14 +148,6 @@ updated since this time will not be updated.  Default: Now.  Expected in ISO
 
     PATCH /notifications/threads/:id
 
-### Input
-
-unread
-: **Boolean** Changes the unread status of the threads.
-
-read
-: **Boolean** Inverse of "unread".
-
 ### Response
 
 <%= headers 205 %>
