@@ -7,9 +7,10 @@ To that end, here are some style guidelines for writing or modifying rulesets.
 They are intended to help and simplify in places where choices are ambiguous,
 but like all guidelines they can be broken if the circumstances require it.
 
-Avoid using the left-wildcard ("&lt;target host='*.example.com'&gt;") unless you
-really mean it. Many rules today specify a left-wildcard target, but the
-rewrite rules only rewrite an explicit list of hostnames.
+Avoid using the left-wildcard ("&lt;target host='*.example.com'&gt;") unless
+you intend to rewrite all or nearly all subdomains.  Many rules today specify
+a left-wildcard target, but the rewrite rules only rewrite an explicit list
+of hostnames.
 
 Instead, prefer listing explicit target hosts and a single rewrite from "^http:" to
 "^https:". This saves you time as a ruleset author because each explicit target
@@ -55,7 +56,14 @@ non-capturing form adds extra line noise that makes rules harder to read.
 Generally you can achieve the same effect by choosing a correspondingly higher
 index for your replacement group to account for the groups you don't care about.
 
-Here is an example ruleset today:
+Avoid snapping redirects. For instance, if https://foo.fm serves HTTPS
+correctly, but redirects to https://foo.com, it's tempting to rewrite foo.fm to
+foo.com, to save users the latency of the redirect. However, such rulesets are
+less obviously correct and require more scrutiny. And the redirect can go out of
+date and cause problems. HTTPS Everywhere rulesets should change requests the minimum
+amount necessary to ensure a secure connection.
+
+Here is an example ruleset pre-style guidelines:
 
 ```
 <ruleset name="WHATWG.org">