summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJan Böcker <jan.boecker@jboecker.de>2013-08-26 11:18:21 +0200
committerTim Graham <timograham@gmail.com>2013-08-27 09:22:51 -0400
commit98635f2a0eda5f161889c16af3e672a01ee9fe3d (patch)
tree329be56b81b823eb9a040b698cb1a8fe0b59b0f1 /docs
parent5547ba743cde37d043c411fd463bcd817dca4302 (diff)
[1.5.x] Fixed typo in docs/topics/conditional-view-processing.txt
Backport of 5fd2c979cb from master
Diffstat (limited to 'docs')
-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 caa7376189..83b454a4aa 100644
--- a/docs/topics/conditional-view-processing.txt
+++ b/docs/topics/conditional-view-processing.txt
@@ -147,7 +147,7 @@ Using the decorators with other HTTP methods
The ``condition`` decorator is useful for more than only ``GET`` and
``HEAD`` requests (``HEAD`` requests are the same as ``GET`` in this
-situation). It can be used also to be used to provide checking for ``POST``,
+situation). It can also be used to provide checking for ``POST``,
``PUT`` and ``DELETE`` requests. In these situations, the idea isn't to return
a "not modified" response, but to tell the client that the resource they are
trying to change has been altered in the meantime.