Merge pull request #2137 from ftobia/patch-1

Fixed typos. Changed grammar.

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/topics/db/sql.txt b/docs/topics/db/sql.txt
index 1369ed84f5..1b806ca42f 100644
--- a/docs/topics/db/sql.txt
+++ b/docs/topics/db/sql.txt
@@ -23,11 +23,11 @@ return model instances:
 
 .. method:: Manager.raw(raw_query, params=None, translations=None)
 
-This method method takes a raw SQL query, executes it, and returns a
+This method takes a raw SQL query, executes it, and returns a
 ``django.db.models.query.RawQuerySet`` instance. This ``RawQuerySet`` instance
-can be iterated over just like an normal QuerySet to provide object instances.
+can be iterated over just like a normal QuerySet to provide object instances.
 
-This is best illustrated with an example. Suppose you've got the following model::
+This is best illustrated with an example. Suppose you have the following model::
 
     class Person(models.Model):
         first_name = models.CharField(...)
@@ -108,7 +108,7 @@ write::
     >>> first_person = Person.objects.raw('SELECT * from myapp_person')[0]
 
 However, the indexing and slicing are not performed at the database level. If
-you have a big amount of ``Person`` objects in your database, it is more
+you have a large number of ``Person`` objects in your database, it is more
 efficient to limit the query at the SQL level::
 
     >>> first_person = Person.objects.raw('SELECT * from myapp_person LIMIT 1')[0]
@@ -323,4 +323,4 @@ is equivalent to:
     try:
         c.execute(...)
     finally:
-        c.close()
\ No newline at end of file
+        c.close()