diff options
| author | Tim Graham <timograham@gmail.com> | 2015-12-31 14:29:52 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-12-31 14:29:52 -0500 |
| commit | 98839e906632dfe77c6f6906d61d62868a0541dc (patch) | |
| tree | 804209f1a293883401d714c0afdf75b3e43da93e /docs/topics/conditional-view-processing.txt | |
| parent | 16411b8400ad08f90c236bb2e18f65c655f903f8 (diff) | |
Removed British/Austrialian word: whilist.
Diffstat (limited to 'docs/topics/conditional-view-processing.txt')
| -rw-r--r-- | docs/topics/conditional-view-processing.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/conditional-view-processing.txt b/docs/topics/conditional-view-processing.txt index ed319474fa..1af587c225 100644 --- a/docs/topics/conditional-view-processing.txt +++ b/docs/topics/conditional-view-processing.txt @@ -184,7 +184,7 @@ Comparison with middleware conditional processing You may notice that Django already provides simple and straightforward conditional ``GET`` handling via the :class:`django.middleware.http.ConditionalGetMiddleware` and -:class:`~django.middleware.common.CommonMiddleware`. Whilst certainly being +:class:`~django.middleware.common.CommonMiddleware`. While certainly being easy to use and suitable for many situations, those pieces of middleware functionality have limitations for advanced usage: |