summaryrefslogtreecommitdiff
path: root/docs/topics/conditional-view-processing.txt
diff options
context:
space:
mode:
authorpp <pp@users.noreply.github.com>2016-01-10 17:48:16 +0100
committerTim Graham <timograham@gmail.com>2016-01-11 18:05:15 -0500
commitb34ff66e5bae3760273255fa5b2525eb21a5eb63 (patch)
treed3cf5e9ea9af2d34bc61122d6bf891553b55472f /docs/topics/conditional-view-processing.txt
parent99d2469e75f1567cbe5ee753563edb68cd51d74a (diff)
Added missing period to "etc.".
Diffstat (limited to 'docs/topics/conditional-view-processing.txt')
-rw-r--r--docs/topics/conditional-view-processing.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/conditional-view-processing.txt b/docs/topics/conditional-view-processing.txt
index 1af587c225..3d667337fd 100644
--- a/docs/topics/conditional-view-processing.txt
+++ b/docs/topics/conditional-view-processing.txt
@@ -6,7 +6,7 @@ HTTP clients can send a number of headers to tell the server about copies of a
resource that they have already seen. This is commonly used when retrieving a
Web page (using an HTTP ``GET`` request) to avoid sending all the data for
something the client has already retrieved. However, the same headers can be
-used for all HTTP methods (``POST``, ``PUT``, ``DELETE``, etc).
+used for all HTTP methods (``POST``, ``PUT``, ``DELETE``, etc.).
For each page (response) that Django sends back from a view, it might provide
two HTTP headers: the ``ETag`` header and the ``Last-Modified`` header. These