nit

diff --git a/docs/markdown/authoritative/modes-of-operation.md b/docs/markdown/authoritative/modes-of-operation.md
index 418a4cf95204d2b2d4686b1d16987eb8956761d3..cdfd55ad6fd156fadef268b9095b66741f0e471c 100644 (file)
--- a/docs/markdown/authoritative/modes-of-operation.md
+++ b/docs/markdown/authoritative/modes-of-operation.md
@@ -8,7 +8,7 @@ MySQL replication has proven to be very robust and well suited, even over transa
 To use native replication, configure your backend storage to do the replication and do not configure PDNS to do so.
 
 # Master operation
-When operating as a master, PDNS sends out notifications of changes to slaves, which react to these notifications by querying PDNS to see if the zone changed, and transferring its contents if it has. Notifications are a way to promptly propagate zone changes to slaves, as described in [RFC 1996](http://tools.ietf.org/html/rfc1996). Since version 4.0, the NOTIFY messages have a TSIG record added (transaction signature) if zone has been configured to use TSIG.
+When operating as a master, PDNS sends out notifications of changes to slaves, which react to these notifications by querying PDNS to see if the zone changed, and transferring its contents if it has. Notifications are a way to promptly propagate zone changes to slaves, as described in [RFC 1996](http://tools.ietf.org/html/rfc1996). Since version 4.0, the NOTIFY messages have a TSIG record added (transaction signature) if zone has been configured to use TSIG and feature has been enabled.
 
 **Warning**: Master support is OFF by default, turn it on by adding [`master`](settings.md#master) to the configuration.