Aug 17, 2015 · Nov 2, 2014 · Nov 2, 2014
diff --git a/content/v3/activity/events/types.md b/content/v3/activity/events/types.md

 Event names are used by [repository webhooks](/v3/repos/hooks/) to specify
 which events the webhook should receive. The included payloads below are from webhook deliveries but
 match events returned by the [Events API](/v3/activity/events/) (except where noted).
 match events returned by the [Events API](/v3/activity/events/) (except where noted). The Events API uses the CamelCased name (e.g. `CommitCommentEvent`) in the `type` field of an event object and does not include the `repository` or `sender` fields in the event payload object.


 Note that some of these events may not be rendered in timelines.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -9,7 +9,7 @@ determined by its event type.

		Event names are used by [repository webhooks](/v3/repos/hooks/) to specify
		which events the webhook should receive. The included payloads below are from webhook deliveries but
		match events returned by the [Events API](/v3/activity/events/) (except where noted).
		match events returned by the [Events API](/v3/activity/events/) (except where noted). The Events API uses the CamelCased name (e.g. `CommitCommentEvent`) in the `type` field of an event object and does not include the `repository` or `sender` fields in the event payload object.


		Note that some of these events may not be rendered in timelines.
Expand Down