about summary refs log tree commit diff
diff options
context:
space:
mode:
authorBrian Anderson <andersrb@gmail.com>2012-10-20 19:44:36 -0700
committerBrian Anderson <andersrb@gmail.com>2012-10-20 19:44:36 -0700
commit082d3d51674203d97fd21e6cda6181b4dccfb2e1 (patch)
treef767a7ec12492e4132f8375bdb6ada95d9e4a102
parent191d16265be6b9db3d48ef87944b7d42b5dffe0d (diff)
parent4edb88112409c111790dacacb06c22de2ef8da06 (diff)
Merge pull request #3823 from paulstansifer/master
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) };