Fixed a mistaken link at the top of both class-based-views docs, and a "content" vs. "context" typo in the topic guide. Thanks to SmileyChris and robhudson for the reports.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@14268 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
4b828a906a
commit
cb33aa1cc8
|
@ -11,7 +11,7 @@ Class-based generic views
|
||||||
|
|
||||||
For details on the previous generic views implementation,
|
For details on the previous generic views implementation,
|
||||||
see the :doc:`topic guide </topics/generic-views>` and
|
see the :doc:`topic guide </topics/generic-views>` and
|
||||||
:doc:`detailed reference </topics/generic-views>`.
|
:doc:`detailed reference </ref/generic-views>`.
|
||||||
|
|
||||||
Writing Web applications can be monotonous, because we repeat certain patterns
|
Writing Web applications can be monotonous, because we repeat certain patterns
|
||||||
again and again. Django tries to take away some of that monotony at the model
|
again and again. Django tries to take away some of that monotony at the model
|
||||||
|
|
|
@ -11,7 +11,7 @@ Class-based generic views
|
||||||
|
|
||||||
For details on the previous generic views implementation,
|
For details on the previous generic views implementation,
|
||||||
see the :doc:`topic guide </topics/generic-views>` and
|
see the :doc:`topic guide </topics/generic-views>` and
|
||||||
:doc:`detailed reference </topics/generic-views>`.
|
:doc:`detailed reference </ref/generic-views>`.
|
||||||
|
|
||||||
Writing Web applications can be monotonous, because we repeat certain patterns
|
Writing Web applications can be monotonous, because we repeat certain patterns
|
||||||
again and again. Django tries to take away some of that monotony at the model
|
again and again. Django tries to take away some of that monotony at the model
|
||||||
|
@ -499,7 +499,7 @@ For example, a simple JSON mixin might look something like this::
|
||||||
# to do much more complex handling to ensure that arbitrary
|
# to do much more complex handling to ensure that arbitrary
|
||||||
# objects -- such as Django model instances or querysets
|
# objects -- such as Django model instances or querysets
|
||||||
# -- can be serialized as JSON.
|
# -- can be serialized as JSON.
|
||||||
return json.dumps(content)
|
return json.dumps(context)
|
||||||
|
|
||||||
Then, you could build a JSON-returning
|
Then, you could build a JSON-returning
|
||||||
:class:`~django.views.generic.detail.DetailView` by mixing your
|
:class:`~django.views.generic.detail.DetailView` by mixing your
|
||||||
|
|
Loading…
Reference in New Issue