Sync changes from upstream repository

Hubot · gjtorikian · commit 90c6f4649d4e · 2014-11-07T15:20:12.000-08:00
diff --git a/content/changes/2012-10-14-rate-limit-changes.html b/content/changes/2012-10-14-rate-limit-changes.html
@@ -11,7 +11,7 @@
 [authenticate](http://developer.github.com/v3/#authentication) via Basic Auth
 or OAuth. Unauthenticated requests will be limited to 60 per hour unless you
 [include your OAuth client and
-secret](http://developer.github.com/v3/#unauthenticated-rate-limited-requests).
+secret](http://developer.github.com/v3/#increasing-the-unauthenticated-rate-limit-for-oauth-applications).
 
 We'll soon require all requests to include a valid [User Agent
 header](http://en.wikipedia.org/wiki/User_agent). Setting a
diff --git a/content/v3.md b/content/v3.md
@@ -233,7 +233,7 @@ $ curl 'https://api.github.com/users/whatever?client_id=xxxx&client_secret=yyyy'
 
 This should only be used in server to server scenarios.  Don't leak your
 OAuth application's client secret to your users.  Read [more about
-unauthenticated rate limiting](#unauthenticated-rate-limited-requests).
+unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications).
 
 ### Failed login limit
 
@@ -333,8 +333,9 @@ Name | Description
 
 For requests using Basic Authentication or OAuth, you can make up to 5,000
 requests per hour. For unauthenticated requests, the rate limit allows you to
-make up to 60 requests per hour. (The Search API has [custom rate limit
-rules](/v3/search/#rate-limit).)
+make up to 60 requests per hour. Unauthenticated requests are associated with your IP address,
+and not the user making requests. Note that [the Search API has custom rate limit
+rules](/v3/search/#rate-limit).
 
 You can check the returned HTTP headers of any API request to see your current
 rate limit status:
@@ -384,11 +385,9 @@ You can also [check your rate limit status](/v3/rate_limit) without incurring an
 API hit.
 <br>
 
-### Unauthenticated rate limited requests
+### Increasing the unauthenticated rate limit for OAuth applications
 
-If you need to make unauthenticated calls but need to use a higher rate limit
-associated with your OAuth application, you can send over your client ID and
-secret in the query string.
+If your OAuth application needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret as part of the query string.
 
 <pre class="terminal">
 $ curl -i 'https://api.github.com/users/whatever?client_id=xxxx&client_secret=yyyy'
diff --git a/content/v3/search.md b/content/v3/search.md
@@ -30,7 +30,7 @@ relevant item to the top of the result list.
 
 The Search API has a custom rate limit. For requests using [Basic
 Authentication](/v3/#authentication), [OAuth](/v3/#authentication), or [client
-ID and secret](/v3/#unauthenticated-rate-limited-requests), you can make up to
+ID and secret](/v3/#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to
 20 requests per minute. For unauthenticated requests, the rate limit allows you
 to make up to 5 requests per minute.
 
