summaryrefslogtreecommitdiff
path: root/docs/topics/conditional-view-processing.txt
diff options
context:
space:
mode:
authorJan Böcker <jan.boecker@jboecker.de>2013-08-26 11:18:21 +0200
committerJan Böcker <jan.boecker@jboecker.de>2013-08-26 11:19:40 +0200
commit5fd2c979cb1289e87b3d2172304106a5b7083459 (patch)
tree7ac8f194717d7906134be5a1abd1dd74549ed792 /docs/topics/conditional-view-processing.txt
parent51a9a5980af3b4762d09c4aa4551d370a1b8b9a8 (diff)
Fixed typo in docs/topics/conditional-view-processing.txt
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 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.