Browse files

Fixed #9412 -- Corrected a couple of typos in the custom model field …

…doc. Thanks carljm.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent d4f4ab8 commit 021b40a84cb0e9f50517ab182e24a6cd469e2a97 @kmtracey kmtracey committed Nov 1, 2008
Showing with 2 additions and 2 deletions.
  1. +2 −2 docs/howto/custom-model-fields.txt
4 docs/howto/custom-model-fields.txt
@@ -437,7 +437,7 @@ for the first time, the ``add`` parameter will be ``True``, otherwise it will be
You only need to override this method if you want to preprocess the value
somehow, just before saving. For example, Django's
-`:class:`~django.db.models.DateTimeField` uses this method to set the attribute
+:class:`~django.db.models.DateTimeField` uses this method to set the attribute
correctly in the case of :attr:`~django.db.models.Field.auto_now` or
@@ -569,7 +569,7 @@ Converting field data for serialization
.. method:: value_to_string(self, obj)
This method is used by the serializers to convert the field into a string for
-output. Calling :meth:``Field._get_val_from_obj(obj)`` is the best way to get the
+output. Calling :meth:`Field._get_val_from_obj(obj)` is the best way to get the
value to serialize. For example, since our ``HandField`` uses strings for its
data storage anyway, we can reuse some existing conversion code::

0 comments on commit 021b40a

Please sign in to comment.