  ``URLField``::
  
      .. versionadded:: 1.5
  
      The current value of the field will be displayed as a clickable link above the
      input widget.
  
  For more information on writing documentation, including an explanation of what
  the ``versionadded`` bit is all about, see
  :doc:`/internals/contributing/writing-documentation`. That page also includes
  an explanation of how to build a copy of the documentation locally, so you can
 
</s> remove The current value of the field will be displayed as a clickable link above the
input widget.
 </s> add     The current value of the field will be displayed as a clickable link above the
    input widget. </s> remove     Raises :exc:`InvalidPage` if previous page doesn't exist.
 </s> add         Raises :exc:`InvalidPage` if previous page doesn't exist. </s> remove         ``success_url`` may contain dictionary string formatting, which
        will be interpolated against the object's field attributes. For
        example, you could use ``success_url="/parent/%(parent_id)s/"`` to
        redirect to a URL composed out of the ``parent_id`` field on a model.
 </s> add             ``success_url`` may contain dictionary string formatting, which
            will be interpolated against the object's field attributes. For
            example, you could use ``success_url="/parent/%(parent_id)s/"`` to
            redirect to a URL composed out of the ``parent_id`` field on a model. </s> remove Some fields in a model won't be deferred, even if you ask for them. You can
never defer the loading of the primary key. If you are using
:meth:`select_related()` to retrieve related models, you shouldn't defer the
loading of the field that connects from the primary model to the related
one, doing so will result in an error.
 </s> add     Some fields in a model won't be deferred, even if you ask for them. You can
    never defer the loading of the primary key. If you are using
    :meth:`select_related()` to retrieve related models, you shouldn't defer the
    loading of the field that connects from the primary model to the related
    one, doing so will result in an error. </s> remove   Previously Django used ``SELECT`` - if not found ``INSERT`` else ``UPDATE``
  algorithm. The old algorithm resulted in one more query in ``UPDATE`` case.
 </s> add     Previously Django used ``SELECT`` - if not found ``INSERT`` else ``UPDATE``
    algorithm. The old algorithm resulted in one more query in ``UPDATE`` case.
        The current value of the field will be displayed as a clickable link above the
        input widget.
  ``URLField``::
  
      .. versionadded:: 1.5
  
        The current value of the field will be displayed as a clickable link above the
        input widget.
        The current value of the field will be displayed as a clickable link above the
        input widget.
  
  For more information on writing documentation, including an explanation of what
  the ``versionadded`` bit is all about, see
  :doc:`/internals/contributing/writing-documentation`. That page also includes
  an explanation of how to build a copy of the documentation locally, so you can
keep keep keep keep replace replace keep keep keep keep keep
 Adapted uses of versionchanged/versionadded to the new form.

Refs #20104. 
docs/intro/contributing.txt