  
  However, **users on 64-bit platforms may experience some problems** using the
  ``reset`` management command. Prior to this change, 64-bit platforms
  would generate a 64-bit, 16 character digest in the constraint name; for
  example::
  
      ALTER TABLE myapp_sometable ADD CONSTRAINT object_id_refs_id_5e8f10c132091d1e FOREIGN KEY ...
  
  Following this change, all platforms, regardless of word size, will generate a
  32-bit, 8 character digest in the constraint name; for example::
 
</s> remove 32-bit, 8 character digest in the constraint name; for example::
 </s> add 32-bit, 8 character digest in the constraint name; for example:

.. code-block:: sql </s> remove :class:`~django.contrib.auth.models.User` object is a string in this format::
 </s> add :class:`~django.contrib.auth.models.User` object is a string in this format:

.. code-block:: text </s> remove explaining how this would work for a dynamically generated web page::
 </s> add explaining how this would work for a dynamically generated web page:

.. code-block:: text </s> remove         # ...
 </s> add         ... </s> remove 2-tuple containing::
 </s> add 2-tuple containing:

.. code-block:: text
example:

.. code-block:: sql
  
  However, **users on 64-bit platforms may experience some problems** using the
  ``reset`` management command. Prior to this change, 64-bit platforms
  would generate a 64-bit, 16 character digest in the constraint name; for
example:

.. code-block:: sql
  
      ALTER TABLE myapp_sometable ADD CONSTRAINT object_id_refs_id_5e8f10c132091d1e FOREIGN KEY ...
  
  Following this change, all platforms, regardless of word size, will generate a
  32-bit, 8 character digest in the constraint name; for example::
keep keep keep keep replace keep keep keep keep keep
 Refs #34140 -- Corrected rst code-block and various formatting issues in docs. 
docs/releases/1.1.txt