diff --git a/README.md b/README.md
index 817f786..627f243 100644
--- a/README.md
+++ b/README.md
@@ -6,12 +6,12 @@ salty-ircd is an [Internet Relay Chat](https://en.wikipedia.org/wiki/Internet_Re
 The main goals of salty-ircd are strict RFC compliance and security.
 
 ### RFC compliance
-salty-ircd aims to be fully compliant with the IRC RFCs, specifically [RFC 1459](https://tools.ietf.org/html/rfc1459), [RFC 2811](https://tools.ietf.org/html/rfc2811), [RFC 2812](https://tools.ietf.org/html/rfc2812), and [RFC 2813](https://tools.ietf.org/html/rfc2813) (planned).
+salty-ircd aims to be fully compliant with the IRC RFCs (in 'RFC mode'), specifically [RFC 1459](https://tools.ietf.org/html/rfc1459), [RFC 2811](https://tools.ietf.org/html/rfc2811), [RFC 2812](https://tools.ietf.org/html/rfc2812), and [RFC 2813](https://tools.ietf.org/html/rfc2813) (planned).
 Newer RFCs take precedence over older RFCs. Errata are respected by default, with newer errata (on the same RFC) taking precedence over older errata.
 
-Any additional features breaking RFC compliance will be made available through compile-time options.
+Any additional features breaking RFC compliance will be made available through compile-time options (i.e. 'non-RFC modes').
 
-### Security
+### Security (non-RFC modes)
  * salty-ircd will require TLS for all connections. An exception could be made to allow hosting a Tor hidden service.
  * salty-ircd will require TLS client certificates for authentication.