Minor tweaks

Author: xaprb

modifying.md

@@ -74,8 +74,10 @@ can call on the database itself, such as `Query()` and so forth.
 
 Prepared statements that are created in a transaction are bound exclusively to
 that transaction, and can't be used outside of it. Likewise, prepared statements
-created only on a database handle can't be used within a transaction. In order to 
-use a Prepared statement prepared outside the transaction, use `Tx.Stmt()`.
+created only on a database handle can't be used within a transaction. To 
+use a prepared statement prepared outside the transaction, use `Tx.Stmt()`,
+which will create a new transaction-specific statement from the one prepared
+outside the transaction.
 
 You should not mingle the use of transaction-related functions such as `Begin()`
 and `Commit()` with SQL statements such as `BEGIN` and `COMMIT` in your SQL

retrieving.md

@@ -112,6 +112,9 @@ defer rows.Close()
 for rows.Next() {
 	// ...
 }
+if err = rows.Err(); err != nil {
+	log.Fatal(err)
+}
 </pre>
 
 Under the hood, `db.Query()` actually prepares, executes, and closes a prepared

surprises.md

@@ -123,7 +123,7 @@ Prepared Statements in Transactions
 ===================================
 
 Caution must be exercised when working with prepared statements in
-transactions.  Consider the following example:
+transactions. Consider the following example:
 
 <pre class="prettyprint lang-go">
 tx, err := db.Begin()
@@ -157,5 +157,8 @@ underlying connection, rendering the connection state inconsistent.
 you should make sure the statement is always closed before the transaction is
 committed or rolled back.
 
+This is a [known issue](https://code.google.com/p/go/issues/detail?id=4459) that
+will probably be fixed in Go 1.4 by [CR 131650043](https://codereview.appspot.com/131650043).
+
 **Previous: [The Connection Pool](connection-pool.html)**
 **Next: [Related Reading and Resources](references.html)**