Capitalized "Python" in docs.

2 files changed, 3 insertions, 3 deletions

diff --git a/docs/ref/migration-operations.txt b/docs/ref/migration-operations.txt
index 31ea32ee9d..a5a74d3be0 100644
--- a/docs/ref/migration-operations.txt
+++ b/docs/ref/migration-operations.txt
@@ -305,7 +305,7 @@ model::
 This is generally the operation you would use to create
 :ref:`data migrations <data-migrations>`, run
 custom data updates and alterations, and anything else you need access to an
-ORM and/or python code for.
+ORM and/or Python code for.
 
 If you're upgrading from South, this is basically the South pattern as an
 operation - one or two methods for forwards and backwards, with an ORM and
diff --git a/docs/ref/models/database-functions.txt b/docs/ref/models/database-functions.txt
index 62b65b8858..3477bd3263 100644
--- a/docs/ref/models/database-functions.txt
+++ b/docs/ref/models/database-functions.txt
@@ -57,7 +57,7 @@ Usage examples::
 
 .. warning::
 
-    A python value passed to ``Coalesce`` on MySQL may be converted to an
+    A Python value passed to ``Coalesce`` on MySQL may be converted to an
     incorrect type unless explicitly cast to the correct database type:
 
     >>> from django.db.models.expressions import RawSQL
@@ -121,7 +121,7 @@ Usage example::
     >>> comments = Comment.objects.annotate(last_updated=Greatest('modified', 'blog__modified'))
     >>> annotated_comment = comments.get()
 
-``annotated_comment.last_updated`` will be the most recent of 
+``annotated_comment.last_updated`` will be the most recent of
 ``blog.modified`` and ``comment.modified``.
 
 .. warning::