diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index 340dcff227..85490d9b9a 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -724,7 +724,7 @@ A :class:`CharField` for a URL. Has one extra optional argument:
The admin represents this as an ```` (a single-line input).
-Like all ::class:`CharField` subclasses, :class:`URLField` takes the optional
+Like all :class:`CharField` subclasses, :class:`URLField` takes the optional
:attr:`~CharField.max_length`argument. If you don't specify
:attr:`~CharField.max_length`, a default of 200 is used.
diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt
index d7c4ee377a..f55ce65699 100644
--- a/docs/ref/models/instances.txt
+++ b/docs/ref/models/instances.txt
@@ -5,7 +5,7 @@ Model instance reference
========================
.. currentmodule:: django.db.models
-
+
This document describes the details of the ``Model`` API. It builds on the
material presented in the :ref:`model ` and :ref:`database
query ` guides, so you'll probably want to read and
@@ -366,8 +366,7 @@ Extra instance methods
In addition to ``save()``, ``delete()``, a model object might get any or all
of the following methods:
-get_FOO_display()
------------------
+.. method:: Model.get_FOO_display()
For every field that has ``choices`` set, the object will have a
``get_FOO_display()`` method, where ``FOO`` is the name of the field. This
@@ -391,8 +390,8 @@ following model::
>>> p.get_gender_display()
'Male'
-get_next_by_FOO(\**kwargs) and get_previous_by_FOO(\**kwargs)
--------------------------------------------------------------
+.. method:: Model.get_next_by_FOO(\**kwargs)
+.. method:: Model.get_previous_by_FOO(\**kwargs)
For every ``DateField`` and ``DateTimeField`` that does not have ``null=True``,
the object will have ``get_next_by_FOO()`` and ``get_previous_by_FOO()``