Commit cb33aa1c authored by Gabriel Hurley's avatar Gabriel Hurley
Browse files

Fixed a mistaken link at the top of both class-based-views docs, and a... 

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
parent 4b828a90

docs/ref/class-based-views.txt

+1 −1
Original line number Diff line number Diff line
@@ -11,7 +11,7 @@ Class-based generic views 


    For details on the previous generic views implementation,

    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

again and again. Django tries to take away some of that monotony at the model

docs/topics/class-based-views.txt

+2 −2
Original line number Diff line number Diff line
@@ -11,7 +11,7 @@ Class-based generic views 


    For details on the previous generic views implementation,

    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

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

            # objects -- such as Django model instances or querysets

            # -- can be serialized as JSON.

            return json.dumps(content)

            return json.dumps(context)



Then, you could build a JSON-returning

:class:`~django.views.generic.detail.DetailView` by mixing your