[nongnu] elpa/emacsql 56a2882936 333/427: Update README for Melpa changes.

[ELPA Syncer]

branch: elpa/emacsql
commit 56a2882936bed450c269983f0018c740f06fd587
Author: Christopher Wellons <wellons@nullprogram.com>
Commit: Christopher Wellons <wellons@nullprogram.com>

    Update README for Melpa changes.
---
 README.md | 20 +++++++++++---------
 1 file changed, 11 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index 9220ab9159..540a7b07ab 100644
--- a/README.md
+++ b/README.md
@@ -14,15 +14,17 @@ closures. EmacSQL has no concept of "TEXT" values; it's all 
just lisp
 objects. The lisp object `nil` corresponds 1:1 with `NULL` in the
 database.
 
-During package installation EmacSQL will attempt to compile a custom
-native binary for communicating with a SQLite database. If this fails
-(a C compiler is not available), it will attempt to download, with
-permission, a pre-built binary when the first database connection is
-attempted. The official sqlite3 command shell is incapable of correct
-interaction when linked with GNU Readline, or when run in Windows, so
-a custom built tool is required. If your own package depends on
-EmacSQL as a database this means it doesn't have to rely on the user
-having any particular software installed.
+On MELPA, each backend is provided as a separate package, suffixed
+with the database name. In the case of `emacsql-sqlite`, on first use
+EmacSQL will attempt to compile a custom native binary for
+communicating with a SQLite database. If this fails (a C compiler is
+not available), it will attempt to download, with permission, a
+pre-built binary when the first database connection is attempted. The
+official sqlite3 command shell is incapable of correct interaction
+when linked with GNU Readline, or when run in Windows, so a custom
+build tool is required. If your own package depends on EmacSQL as a
+database, this means it doesn't have to rely on the user having any
+particular software installed.
 
 Requires Emacs 24.3 or later.