fixed discussion about anywhere

grosu · grosu · commit d7dcdafaa826 · 2016-01-12T13:07:54.000-06:00
Former-commit-id: ae98a7c99ec6a1c7aed79ecfa328e9b5960c7bee [formerly 2365b489d8ad1b26185615825082168a7e7b3dca]
Former-commit-id: 23d23c4aa68ea6c37550c64ce1aaa9d3dfff1962
diff --git a/k-distribution/tutorial/1_k/2_imp/lesson_4/README.md b/k-distribution/tutorial/1_k/2_imp/lesson_4/README.md
@@ -99,11 +99,9 @@ As seen soon when we define IMP++, configuration abstraction is not only a
 user convenience; it actually significantly increases the modularity of our
 definitions.  The k-cell-completion is only the very first step, though.
 
-If you really want certain rewrites over syntactic terms to simply apply
+If you really want certain rewrites over syntactic terms to apply
 anywhere they match, then you should tag the rule with the attribute
-`anywhere`, which tells the tool to not complete the rule and thus allows
-it to apply anywhere.  We will discuss tags, and in particular the
-`anywhere` tag, in future tutorial lessons.
+`anywhere`, which was discussed in Tutorial 1, Lesson 2.5.
 
 #### Structural vs. Computational Rules
 
diff --git a/k-distribution/tutorial/NOTES.md b/k-distribution/tutorial/NOTES.md
@@ -16,6 +16,7 @@ Things to revise each time the structure of the tutorial changes:
 
 * `1_k\2_imp\lesson_1\README.md` refers to Tutorial 1
 * `1_k\2_imp\lesson_4\README.md` refers to Lesson 1
+* `1_k\2_imp\lesson_4\README.md` refers to Tutorial 1, Lesson 2.5
 * `1_k\3_lambda++\lesson_1\README.md` refers to Lesson 8, Tutorial 1
 * `1_k\3_lambda++\lesson_2\README.md` Lesson 1, Tutorial 1
 * `1_k\3_lambda++\lesson_3\README.md` refers to Lesson 7, Tutorial 1
