From 46be81115a9a6737da6a28f34004f7352129e0da Mon Sep 17 00:00:00 2001
From: Brett Bieber <brett.bieber@gmail.com>
Date: Thu, 23 Aug 2012 08:41:19 -0500
Subject: [PATCH] Minor spelling correction & grammatical formatting

---
 en/tutorials/getting-started-database.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/en/tutorials/getting-started-database.rst b/en/tutorials/getting-started-database.rst
index 77392e473..c625193ae 100644
--- a/en/tutorials/getting-started-database.rst
+++ b/en/tutorials/getting-started-database.rst
@@ -7,7 +7,7 @@ Getting Started: Database First
     start with developing Objects and then map them onto your database. When
     you :doc:`Model First <getting-started-models>`, you are modelling your application using tools (for
     example UML) and generate database schema and PHP code from this model.
-    When you have a :doc:`Database First <getting-started-database>`, then you already have a database schema
+    When you have a :doc:`Database First <getting-started-database>`, you already have a database schema
     and generate the corresponding PHP code from it.
 
 .. note::
@@ -18,10 +18,10 @@ Development of new applications often starts with an existing database schema.
 When the database schema is the starting point for your application, then
 development is said to use the *Database First* approach to Doctrine.
 
-In this workflow you would always do changes to the database schema and then
+In this workflow you would modify the database schema first and then
 regenerate the PHP code to use with this schema. You need a flexible
 code-generator for this task and up to Doctrine 2.2, the code generator hasn't
 been flexible enough to achieve this.
 
-We spinned of a subproject Doctrine CodeGenerator that will fill this gap and
+We spinned off a subproject, Doctrine CodeGenerator, that will fill this gap and
 allow you to do *Database First* development.