Skip to content

Commit

Permalink
Fixed #9412 -- Corrected a couple of typos in the custom model field …
Browse files Browse the repository at this point in the history
…doc. Thanks carljm.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9314 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information
kmtracey committed Nov 1, 2008
1 parent d4f4ab8 commit 021b40a
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/howto/custom-model-fields.txt
Expand Up @@ -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
:attr:`~django.db.models.Field.auto_now_add`.

Expand Down Expand Up @@ -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::

Expand Down

0 comments on commit 021b40a

Please sign in to comment.