Fixed #13530: Corrected a handful of doc typos. Thanks Ramiro.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@13247 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/howto/static-files.txt

@@ -40,7 +40,7 @@ How to do it
 
 Here's the formal definition of the :func:`~django.views.static.serve` view:
 
-.. function:: def serve(request, path, document_root, show_indexes=False):
+.. function:: def serve(request, path, document_root, show_indexes=False)
 
 To use it, just put this in your :ref:`URLconf <topics-http-urls>`::
 

docs/releases/1.2.txt

@@ -351,8 +351,8 @@ people this shouldn't have been a problem because ``bool`` is a subclass of
 only time this should ever be an issue is if you were expecting printing the
 ``repr`` of a ``BooleanField`` to print ``1`` or ``0``.
 
-Changes to the interpretation of``max_num`` in FormSets
--------------------------------------------------------
+Changes to the interpretation of ``max_num`` in FormSets
+--------------------------------------------------------
 
 As part of enhancements made to the handling of FormSets, the default
 value and interpretation of the ``max_num`` parameter to the

docs/topics/forms/modelforms.txt

@@ -674,7 +674,7 @@ to ``modelformset_factory`` to limit the number of extra forms displayed.
     >>> [x.name for x in formset.get_queryset()]
     [u'Charles Baudelaire', u'Paul Verlaine', u'Walt Whitman']
 
-If the value of ``max_num`` is geater than the number of existing related
+If the value of ``max_num`` is greater than the number of existing related
 objects, up to ``extra`` additional blank forms will be added to the formset,
 so long as the total number of forms does not exceed ``max_num``::
 

docs/topics/pagination.txt

@@ -221,7 +221,7 @@ them both with a simple ``except InvalidPage``.
 ``Page`` objects
 ================
 
-.. class:: Page(object_list, number, paginator):
+.. class:: Page(object_list, number, paginator)
 
 You usually won't construct :class:`Pages <Page>` by hand -- you'll get them
 using :meth:`Paginator.page`.