Playground cleanup

Just a little bit of editing.

Signed-off-by: Stephen Celis <[email protected]>

Author: stephencelis

SQLite.playground/Documentation/fragment-3.html

@@ -4,7 +4,7 @@
 <meta id='xcode-display' name='xcode-display' content='render'>
 <section>
     <p>
-        Prepared statements can bind and escape input values safely. In this case, both <code>email</code> and <code>admin</code> column values are marked and bound with different values over two executions.
+        Prepared statements can bind and escape input values safely. In this case, both <code>email</code> and <code>admin</code> columns are bound with different values over two executions.
     </p>
     <p>
         The <code>Database</code> class exposes information about recently run queries via several properties: <code>totalChanges</code> returns the total number of changes (inserts, updates, and deletes) since the connection was opened; <code>lastChanges</code> returns the number of changes from the last executed statement that modified the database; <code>lastID</code> returns the row ID of the last insert.

SQLite.playground/Documentation/fragment-4.html

@@ -5,6 +5,6 @@
 <section>
     <h3>Querying</h3>
     <p>
-        <code>Statement</code> objects act as Swift sequences <em>and</em> generators. We can iterate over a select statement’s rows directly using a <code>for</code>–<code>in</code> loop.
+        <code>Statement</code> objects act as both sequences <em>and</em> generators. We can iterate over a select statement’s rows directly using a <code>for</code>–<code>in</code> loop.
     </p>
 </section>

SQLite.playground/Documentation/fragment-6.html

@@ -14,6 +14,6 @@ <h4>Experiment</h4>
     </aside>
     <h3>Transactions &amp; Savepoints</h3>
     <p>
-        Using the <code>transaction</code> and <code>savepoint</code> functions, we can run a series of statements, commiting the changes to the database if all succeed, or bailing out early and rolling back on failure. In the following example we prepare two statements: one to insert a manager into the database, and one—given a manager’s row ID—to insert a managed user into the database.
+        Using the <code>transaction</code> and <code>savepoint</code> functions, we can run a series of statements, commiting the changes to the database if they all succeed. If a single statement fails, we bail out early and roll back. In the following example we prepare two statements: one to insert a manager into the database, and one—given a manager’s row ID—to insert a managed user into the database.
     </p>
 </section>

SQLite.playground/Documentation/fragment-8.html

@@ -4,6 +4,6 @@
 <meta id='xcode-display' name='xcode-display' content='render'>
 <section>
     <p>
-        Our database has a uniqueness constraint on email address, so let’s try inserting Fiona, who also claims to be managing Emery.
+        Our database has a uniqueness constraint on email address, so let’s see what happens when we insert Fiona, who also claims to be managing Emery.
     </p>
 </section>

SQLite.playground/section-10.swift

@@ -1,3 +1,3 @@
 for row in db.prepare("SELECT id, email FROM users") {
-    println(row)
+    println("id: \(row[0]), email: \(row[1])")
 }