diff --git a/reference/mysqlnd_ms/changes.xml b/reference/mysqlnd_ms/changes.xml
index 74f86e0bdd..a40fbb82e8 100644
--- a/reference/mysqlnd_ms/changes.xml
+++ b/reference/mysqlnd_ms/changes.xml
@@ -58,6 +58,33 @@
       is opened. This is most useful when using lazy connections, which are a default.
      </para>
     </listitem>
+    <listitem>
+     <para>
+      Introduced <literal>wait_for_gtid_timeout</literal> setting to throttle
+      slave reads that need session consistency. If global transaction identifier are
+      used and the service level is set to session consistency, the plugin
+      tries to find up-to-date slaves. The slave status check is done by
+      a SQL statement. If nothing else is set, the slave status is checked only
+      one can the search for more up-to-date slaves continues immediately
+      thereafter. Setting <literal>wait_for_gtid_timeout</literal> instructs the plugin
+      to poll a slaves status for <literal>wait_for_gtid_timeout</literal> seconds
+      if the first execution of the SQL statement has shown that the slave is not
+      up-to-date yet. The poll will be done once per second. This way, the plugin
+      will wait for slaves to catch up and throttle the client.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      New failover strategy <literal>loop_before_master</literal>.
+      By default the plugin does no failover. It is possible to enable
+      automatic failover if a connection attempt fails. Upto version 1.3
+      only <literal>master</literal> stategy existed to failover to a master if
+      a slave connection fails. <literal>loop_before_master</literal> is
+      similar but tries all other slaves before attempting to connect to the master
+      if a slave connection fails. The number of attempts can be limited using
+      the <literal>max_retries</literal> option.
+     </para>
+    </listitem>
    </itemizedlist>
   </para>
  </section>