[trafficcontrol] branch master updated: Fixing some grammatical mistakes.

[ra...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rawlin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git


The following commit(s) were added to refs/heads/master by this push:
     new dfbfc3a  Fixing some grammatical mistakes.
dfbfc3a is described below

commit dfbfc3a5f66a28b00d6754ee17ec831a2ea65198
Author: JordanBrosch <Jo...@gmail.com>
AuthorDate: Tue Aug 14 13:45:14 2018 -0400

    Fixing some grammatical mistakes.
---
 docs/source/basics/cache_revalidation.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/source/basics/cache_revalidation.rst b/docs/source/basics/cache_revalidation.rst
index dc57346..980ca53 100644
--- a/docs/source/basics/cache_revalidation.rst
+++ b/docs/source/basics/cache_revalidation.rst
@@ -34,7 +34,7 @@ The `HTTP/1.1 spec <https://www.ietf.org/rfc/rfc2616.txt>`_ allows for origin se
 
   <html><body>This is a fun file</body></html>
 
-In the above response, the origin server tells downstream caching systems that the maximum time to cache this response for is 86400 seconds. The origin can also add a ``Expires:`` header, explicitly telling the cache the time this response is to be expired. When a response is expired it usually doesn't get deleted from the cache, but, when a request comes in that would have hit on this response if it was not expired, the cache *revalidates* the response. In stead of requesting the object [...]
+In the above response, the origin server tells downstream caching systems that the maximum time to cache this response for is 86400 seconds. The origin can also add a ``Expires:`` header, explicitly telling the cache the time this response is to be expired. When a response is expired it usually doesn't get deleted from the cache, but, when a request comes in that would have hit on this response if it was not expired, the cache *revalidates* the response. Instead of requesting the object  [...]
 
 	GET /foo/bar/fun.html HTTP/1.1
 	If-None-Match: "1aa008f-2d-50a3559482cc0"
@@ -68,4 +68,4 @@ If the Content did not change (meaning, the response would have had the same ETa
   Content-Type: text/html; charset=UTF-8
 
 Note that the 304 response only has headers, not the data.
- 
\ No newline at end of file
+