Update docs for caching headers

jasonrudolph · jasonrudolph · commit a7e42ecc399f · 2013-10-09T13:23:40.000-04:00
- Most 200/201 responses include an ETag header
- For single-object resources (e.g., a user, an issue, etc.), most 200/201
  responses include a Last-Modified header (i.e., the timestamp for the last
  time that resource changed). For list resources (e.g., a list of users, a list
  of issues, etc.), most responses will *not* include the Last-Modified header.
diff --git a/content/v3.md b/content/v3.md
@@ -383,9 +383,9 @@ User-Agent: Awesome-Octocat-App
 
 ## Conditional requests
 
-Most responses return `Last-Modified` and `ETag` headers. You can use the values
+Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values
 of these headers to make subsequent requests to those resources using the
-`If-Modified-Since` and `If-None-Match` headers, respectively. If the resource
+`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource
 has not changed, the server will return a `304 Not Modified`. Also note: making
 a conditional request and receiving a 304 response does not count against your
 [Rate Limit](#rate-limiting), so we encourage you to use it whenever possible.
