From c4e2e4f630fd86cb9993daf874c1a8964e4b92f8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20B=C3=B6cker?= Date: Mon, 26 Aug 2013 11:18:21 +0200 Subject: [PATCH] [1.6.x] Fixed typo in docs/topics/conditional-view-processing.txt Backport of 5fd2c979cb from master --- docs/topics/conditional-view-processing.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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.