Minor doc tweaks.

Author: pitfield

Docs/faq.md

@@ -24,4 +24,4 @@ Postgres doesn't require the columns returned by a `SELECT` to be uniquely named
 
 ### In retrieving the value of a column, why do I need to specify the Swift type?
 
-To make Postgres-to-Swift type conversion explicit and robust, PostgresClientKit defers to the developer.  Should a SQL `NUMERIC` map to a Swift `Int`, `Double`, or `Decimal`?  Should a SQL `VARCHAR` map to a Swift `String` or an `Optional<String>`?  Ultimately answering these questions requires domain knowledge, which may not be encoded in the SQL data model, but which (hopefully) the developer has.
+To make Postgres-to-Swift type conversion explicit and robust, PostgresClientKit defers to the developer.  Should a SQL `NUMERIC` map to a Swift `Int`, `Double`, or `Decimal`?  Should a SQL `VARCHAR` map to a Swift `String` or an `Optional<String>`?  Answering these questions requires domain knowledge, which may not be encoded in the SQL data model, but which the developer (hopefully) has.

Docs/troubleshooting.md

@@ -51,7 +51,7 @@ Review the [`pg_hba.conf`](https://www.postgresql.org/docs/11/auth-pg-hba-conf.h
 
 ## Cursor is unexpectedly closed
 
-The deinitializers of `Connection`, `Statement`, and `Cursor` call `close()` on instances of those types.  This is normally a convenient way to ensure Postgres resources are released, but can have unexpected side effects, particular for `Statement`.  For example:
+The deinitializers of `Connection`, `Statement`, and `Cursor` call `close()` on instances of those types.  This is normally a convenient way to ensure Postgres resources are released, but can have unexpected side effects, particularly for `Statement`.  For example:
 
 ```swift
 // Perform a first SQL command.

README.md

@@ -158,7 +158,7 @@ Please use [issues](../../issues) to:
 - report problems (bugs)
 - request enhancements
 
-Pull requests are welcomed.  For a non-trivial contribution (for example, more than correcting spelling, typos, or whitespace) please first discuss the proposed change by opening an issue.
+Pull requests against the `develop` branch are welcomed.  For a non-trivial contribution (for example, more than correcting spelling, typos, or whitespace) please first discuss the proposed change by opening an issue.
 
 ## License