# HG changeset patch
# User Matthew Wild <mwild1@gmail.com>
# Date 1686219940 -3600
# Node ID a8f49bf7f8e639cb9ef84792de3108e228ba653d
# Parent  ce6e071d61a0fd9a777eb62035e6b25acca2e358
mod_firewall: README: Add some emphasis on the exact behaviour of TO FULL JID

diff -r ce6e071d61a0 -r a8f49bf7f8e6 mod_firewall/README.markdown
--- a/mod_firewall/README.markdown	Wed Jun 07 15:59:34 2023 +0200
+++ b/mod_firewall/README.markdown	Thu Jun 08 11:25:40 2023 +0100
@@ -260,7 +260,7 @@
   `FROM`        The JID in the 'from' attribute matches the given JID.
   `TO`          The JID in the 'to' attribute matches the given JID.
   `TO SELF`     The stanza is sent by any of a user's resources to their own bare JID.
-  `TO FULL JID` The stanza is addressed to a valid full JID on the local server (full JIDs include a resource at the end, and only exist for the lifetime of a single session, therefore the recipient must be online, or this check will not match).
+  `TO FULL JID` The stanza is addressed to a **valid** full JID on the local server (full JIDs include a resource at the end, and only exist for the lifetime of a single session, therefore the recipient **must be online**, or this check will not match).
 
 The TO and FROM conditions both accept wildcards in the JID when it is
 enclosed in angle brackets ('\<...\>'). For example: