about summary refs log tree commit diff
diff options
context:
space:
mode:
authorSteven Allen <steven@stebalien.com>2015-05-20 17:19:57 -0400
committerSteven Allen <steven@stebalien.com>2015-05-20 17:19:57 -0400
commit74fadfaeeaa31ec8ef92622c009131990dd9a936 (patch)
tree19f184d9944196bc5a1118ddd4c10473853beef6
parentd7185dcff12a6963535e73ed4b0f392da236068c (diff)
downloadrust-74fadfaeeaa31ec8ef92622c009131990dd9a936.tar.gz
rust-74fadfaeeaa31ec8ef92622c009131990dd9a936.zip
Change "must" to "may only" in macro future proofing rules.
They don't have to be followed by anything.
-rw-r--r--src/doc/trpl/macros.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/doc/trpl/macros.md b/src/doc/trpl/macros.md
index cc7d9b595f9..a45d4824f41 100644
--- a/src/doc/trpl/macros.md
+++ b/src/doc/trpl/macros.md
@@ -476,9 +476,9 @@ which syntactic form it matches.
 
 There are additional rules regarding the next token after a metavariable:
 
-* `expr` variables must be followed by one of: `=> , ;`
-* `ty` and `path` variables must be followed by one of: `=> , : = > as`
-* `pat` variables must be followed by one of: `=> , =`
+* `expr` variables may only be followed by one of: `=> , ;`
+* `ty` and `path` variables may only be followed by one of: `=> , : = > as`
+* `pat` variables may only be followed by one of: `=> , =`
 * Other variables may be followed by any token.
 
 These rules provide some flexibility for Rust’s syntax to evolve without