diff --git a/plugin/autopath/autopath.go b/plugin/autopath/autopath.go
index 8583988d9..4db9366d2 100644
--- a/plugin/autopath/autopath.go
+++ b/plugin/autopath/autopath.go
@@ -5,7 +5,7 @@ client's search path resolution by performing these lookups on the server...
 The server has a copy (via AutoPathFunc) of the client's search path and on
 receiving a query it first establishes if the suffix matches the FIRST configured
 element. If no match can be found the query will be forwarded up the plugin
-chain without interference (if 'fallthrough' has been set).
+chain without interference (if, and only if, 'fallthrough' has been set).
 
 If the query is deemed to fall in the search path the server will perform the
 queries with each element of the search path appended in sequence until a
diff --git a/plugin/dnssec/dnskey.go b/plugin/dnssec/dnskey.go
index 5c67fca08..6ca89802e 100644
--- a/plugin/dnssec/dnskey.go
+++ b/plugin/dnssec/dnskey.go
@@ -83,12 +83,12 @@ func (d Dnssec) getDNSKEY(state request.Request, zone string, do bool, server st
 	return m
 }
 
-// Return true if this is a zone key with the SEP bit unset. This implies a ZSK (rfc4034 2.1.1).
+// Return true if, and only if, this is a zone key with the SEP bit unset. This implies a ZSK (rfc4034 2.1.1).
 func (k DNSKEY) isZSK() bool {
 	return k.K.Flags&(1<<8) == (1<<8) && k.K.Flags&1 == 0
 }
 
-// Return true if this is a zone key with the SEP bit set. This implies a KSK (rfc4034 2.1.1).
+// Return true if, and only if, this is a zone key with the SEP bit set. This implies a KSK (rfc4034 2.1.1).
 func (k DNSKEY) isKSK() bool {
 	return k.K.Flags&(1<<8) == (1<<8) && k.K.Flags&1 == 1
 }