diff options
| author | Christoph Zwerschke <cito@online.de> | 2018-01-29 15:25:23 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2018-01-29 12:48:37 -0500 |
| commit | d4bbd3f41882104156cf9f2b02cb13376a59489d (patch) | |
| tree | d6b0c0b7243ba04b3ad4c18f51b0e5b448cfc6e1 /docs/intro/tutorial05.txt | |
| parent | e6f0e324e28bc7d0c125415de871466aa1f4b983 (diff) | |
Corrected an explanation in tutorial 5.
Diffstat (limited to 'docs/intro/tutorial05.txt')
| -rw-r--r-- | docs/intro/tutorial05.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/intro/tutorial05.txt b/docs/intro/tutorial05.txt index 304ec1ff0b..1f6a53ebee 100644 --- a/docs/intro/tutorial05.txt +++ b/docs/intro/tutorial05.txt @@ -134,8 +134,8 @@ right away: the ``Question.was_published_recently()`` method returns ``True`` if the ``Question`` was published within the last day (which is correct) but also if the ``Question``’s ``pub_date`` field is in the future (which certainly isn't). -To check if the bug really exists, using the Admin create a question whose date -lies in the future and check the method using the :djadmin:`shell`: +Confirm the bug by using the :djadmin:`shell` to check the method on a question +whose date lies in the future: .. console:: |