  
  :class:`~django.views.generic.base.TemplateResponseMixin`
      Every built in view which returns a
      :class:`~django.template.response.TemplateResponse` will call the
      :meth:`~django.views.generic.base.TemplateResponseMixin.render_to_response`
      method that ``TemplateResponseMixin`` provides. Most of the time this
      will be called for you (for instance, it is called by the ``get()`` method
      implemented by both :class:`~django.views.generic.base.TemplateView` and
      :class:`~django.views.generic.detail.DetailView`); similarly, it's unlikely
      that you'll need to override it, although if you want your response to
 
</s> remove     :meth:`~django.views.generic.base.ContextMixin.get_context_data` passing
 </s> add     :meth:`~django.views.generic.base.ContextMixin.get_context_data()` passing </s> remove     ``get_context_data`` returns a dictionary; in ``ContextMixin`` it
 </s> add     ``get_context_data()`` returns a dictionary; in ``ContextMixin`` it </s> remove     ``render_to_response`` itself calls
 </s> add     ``render_to_response()`` itself calls </s> remove :meth:`~django.views.generic.base.ContextMixin.get_context_data` to
 </s> add :meth:`~django.views.generic.base.ContextMixin.get_context_data()` to </s> remove     for ``get_object`` so we'll override that method and have it return
 </s> add     for ``get_object()`` so we'll override that method and have it return
    :meth:`~django.views.generic.base.TemplateResponseMixin.render_to_response()`
  
  :class:`~django.views.generic.base.TemplateResponseMixin`
      Every built in view which returns a
      :class:`~django.template.response.TemplateResponse` will call the
    :meth:`~django.views.generic.base.TemplateResponseMixin.render_to_response()`
      method that ``TemplateResponseMixin`` provides. Most of the time this
      will be called for you (for instance, it is called by the ``get()`` method
      implemented by both :class:`~django.views.generic.base.TemplateView` and
      :class:`~django.views.generic.detail.DetailView`); similarly, it's unlikely
      that you'll need to override it, although if you want your response to
keep keep keep keep replace keep keep keep keep keep
 Fixed #20658 -- Fixed bad reST formatting and missing parentheses in the docs for CBV mixins

Thanks to Keryn Knight for the report. 
docs/topics/class-based-views/mixins.txt