about summary refs log tree commit diff
diff options
context:
space:
mode:
authorPaul Stansifer <paul.stansifer@gmail.com>2012-10-20 21:54:25 -0400
committerPaul Stansifer <paul.stansifer@gmail.com>2012-10-20 21:54:25 -0400
commit4edb88112409c111790dacacb06c22de2ef8da06 (patch)
tree88b49a0916d2b8237ca791c90239fbed17da7e0e
parent837875711a8724784e401ee5ef2fecad006a0ca6 (diff)
downloadrust-4edb88112409c111790dacacb06c22de2ef8da06.tar.gz
rust-4edb88112409c111790dacacb06c22de2ef8da06.zip
Talk about ends, rather than means, in macro tutorial introduction.
-rw-r--r--doc/tutorial-macros.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/tutorial-macros.md b/doc/tutorial-macros.md
index c7e1ada648e..40cbcacf1e1 100644
--- a/doc/tutorial-macros.md
+++ b/doc/tutorial-macros.md
@@ -2,11 +2,11 @@
 
 # Introduction
 
-Functions are the primary tool that programmers can use to build
-abstractions. Sometimes, though, programmers want to abstract over
-compile-time, syntactic structures rather than runtime values. For example,
-the following two code fragments both pattern-match on their input and return
-early in one case, doing nothing otherwise:
+Functions are the primary tool that programmers can use to build abstractions.
+Sometimes, however, programmers want to perform abstractions over things that are not
+runtime values. Macros provide a syntactic abstraction. For an example of how this
+can be useful, consider the following two code fragments, which both pattern-match
+on their input and return early in one case, and do nothing otherwise:
 
 ~~~~
 # enum t { special_a(uint), special_b(uint) };