diff --git a/reference/mysqlnd_ms/book.xml b/reference/mysqlnd_ms/book.xml
index 409a0aa8e7..5a3b03b410 100755
--- a/reference/mysqlnd_ms/book.xml
+++ b/reference/mysqlnd_ms/book.xml
@@ -197,7 +197,7 @@
- Support for built-in global transaction identifier feature of MySQL 5.6.5-m8 or newer.
+ Support for built-in global transaction identifier feature of MySQL 5.6.5 or newer.
@@ -247,15 +247,15 @@
- Servers of a replication cluster can be organized in groups.
- Queries can be manually directed to to a specific group using a SQL hint.
- Grouping can be used to partition (shard) data, or to cure the issue of
- hotspots in update anywhere setups.
+ Servers of a replication cluster can be organized into groups. SQL hints
+ can be used to manually direct queries to a specific group.
+ Grouping can be used to partition (shard) the data, or to cure the issue of
+ hotspots with updates.
- MySQL Replication filter are supported through the table filter.
+ MySQL Replication filters are supported through the table filter.
diff --git a/reference/mysqlnd_ms/changes.xml b/reference/mysqlnd_ms/changes.xml
index 8c1b73ad07..6b8615a3af 100644
--- a/reference/mysqlnd_ms/changes.xml
+++ b/reference/mysqlnd_ms/changes.xml
@@ -54,31 +54,31 @@
- Introduced node_group filter.
+ Introduced the node_group filter.
The filter lets you organize servers (master and slaves)
- in groups. Queries can be directed to a certain group of servers
+ into groups. Queries can be directed to a certain group of servers
by prefixing the query statement with a SQL hint/comment that contains
- a groups configuration name. Grouping can be used for
- partitioning and sharding but also to optimize for cache locality.
- In case of sharding, think of a group name as a shard key.
+ the groups configured name. Grouping can be used for
+ partitioning and sharding, and also to optimize for local caching.
+ In the case of sharding, a group name can be thought of like a shard key.
All queries for a given shard key will be executed on the
- configured shard. Please, note that sharding setups require
- both client and server support.
+ configured shard. Note: both the client and server must support sharding
+ for sharding to function with mysqlnd_ms.
Extended configuration file validation during PHP startup (RINIT).
- A warning will be thrown if the configuration file can not be read, is empty
- or parsing the JSON failed. Please note, execution is not halted.
- Warnings may appear in log files only depending on your PHP deployment.
- Distributions that aim to provide a pre-configured setup including a
- configuration file stub are asked to put {} into
- the configuration file to prevent any warnings about an invalid
- configuration.
+ An E_WARNING level error will be thrown if the configuration
+ file can not be read (permissions), is empty, or the file (JSON) could not be parsed.
+ Warnings may appear in log files, which depending on how PHP is configured.
+ Distributions that aim to provide a pre-configured setup, including a
+ configuration file stub, are asked to put {} into
+ the configuration file to prevent this warning about an invalid
+ configuration file.
- Code examples from the source distribution have been updated.
+ The code examples in the mysqlnd_ms source were updated.