Merge pull request #230 from pjdelport/cleanup

Cleanup

2 files changed, 2 insertions, 2 deletions

diff --git a/django/forms/models.py b/django/forms/models.py
index 0831d5f4b2..4d56f1d38a 100644
--- a/django/forms/models.py
+++ b/django/forms/models.py
@@ -714,7 +714,7 @@ class BaseInlineFormSet(BaseModelFormSet):
             # Remove the foreign key from the form's data
             form.data[form.add_prefix(self.fk.name)] = None
 
-        # Set the fk value here so that the form can do it's validation.
+        # Set the fk value here so that the form can do its validation.
         setattr(form.instance, self.fk.get_attname(), self.instance.pk)
         return form
 
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
index 1f4d09f6cb..74e6b48f07 100644
--- a/docs/ref/databases.txt
+++ b/docs/ref/databases.txt
@@ -111,7 +111,7 @@ outputs a single ``CREATE INDEX`` statement.  However, if the database type
 for the field is either ``varchar`` or ``text`` (e.g., used by ``CharField``,
 ``FileField``, and ``TextField``), then Django will create
 an additional index that uses an appropriate `PostgreSQL operator class`_
-for the column.  The extra index is necessary to correctly perfrom
+for the column.  The extra index is necessary to correctly perform
 lookups that use the ``LIKE`` operator in their SQL, as is done with the
 ``contains`` and ``startswith`` lookup types.