  :class:`~django.db.models.DateTimeField` that does not have :attr:`null=True
  <django.db.models.Field.null>`, the object will have ``get_next_by_FOO()`` and
  ``get_previous_by_FOO()`` methods, where ``FOO`` is the name of the field. This
  returns the next and previous object with respect to the date field, raising
  a :exc:`~django.db.DoesNotExist` exception when appropriate.
  
  Both methods accept optional keyword arguments, which should be in the format
  described in :ref:`Field lookups <field-lookups>`.
  
  Note that in the case of identical date values, these methods will use the
 
</s> remove         :class:`~django.db.models.fields.DateField` or
        :class:`~django.db.models.fields.DateTimeField` on the model for which
 </s> add         :class:`~django.db.models.DateField` or
        :class:`~django.db.models.DateTimeField` on the model for which </s> remove :exc:`~django.core.excpetions.MultipleObjectsReturned` exception is an
 </s> add :exc:`~django.core.exceptions.MultipleObjectsReturned` exception is an </s> remove Note that if a :class:`~django.forms.fields.Field` defines
:attr:`~Form.initial` *and* you include ``initial`` when instantiating the
``Form``, then the latter ``initial`` will have precedence. In this example,
``initial`` is provided both at the field level and at the form instance level,
and the latter gets precedence::
 </s> add Note that if a :class:`~django.forms.Field` defines :attr:`~Form.initial` *and*
you include ``initial`` when instantiating the ``Form``, then the latter
``initial`` will have precedence. In this example, ``initial`` is provided both
at the field level and at the form instance level, and the latter gets
precedence:: </s> remove         :class:`~django.db.models.fields.BooleanField` on the model
 </s> add         :class:`~django.db.models.BooleanField` on the model </s> remove         :class:`datetime` value into a list with date and time split into two
        separate values::
 </s> add         :class:`~datetime.datetime` value into a list with date and time split
        into two separate values::
a :exc:`~django.core.exceptions.DoesNotExist` exception when appropriate.
  :class:`~django.db.models.DateTimeField` that does not have :attr:`null=True
  <django.db.models.Field.null>`, the object will have ``get_next_by_FOO()`` and
  ``get_previous_by_FOO()`` methods, where ``FOO`` is the name of the field. This
  returns the next and previous object with respect to the date field, raising
a :exc:`~django.core.exceptions.DoesNotExist` exception when appropriate.
  
  Both methods accept optional keyword arguments, which should be in the format
  described in :ref:`Field lookups <field-lookups>`.
  
  Note that in the case of identical date values, these methods will use the
keep keep keep keep replace keep keep keep keep keep
 Fixed broken links, round 3. refs #19516 
docs/ref/models/instances.txt