Index: doc/next-tutorial/next-tutorial.txt =================================================================== diff -u -rd725e5e4cfc9f89d78e781e6ce27900e199ba8c5 -rf934951db464db1a6f39ac98290ecde17a466cd7 --- doc/next-tutorial/next-tutorial.txt (.../next-tutorial.txt) (revision d725e5e4cfc9f89d78e781e6ce27900e199ba8c5) +++ doc/next-tutorial/next-tutorial.txt (.../next-tutorial.txt) (revision f934951db464db1a6f39ac98290ecde17a466cd7) @@ -1,7 +1,7 @@ Tutorial for the Next Scripting Language ========================================== Gustaf Neumann , Stefan Sobernig -v2.0.0, November 2014: +v2.1.0, December 2016: Written for the Initial Release of the Next Scripting Framework. :Author Initials: GN :toc: @@ -1532,7 +1532,7 @@ current object (therefore, the call is equivalent to +d1 foo+). The next three calls show how to provide flags that influence the method resolution. The flags can be provided between the colon and the method -name. These flags are used rather seldomly but can be helpful in some +name. These flags are used rather seldom but can be helpful in some situations. The invocation flag +-local+ means that the method has to be resolved @@ -1964,7 +1964,7 @@ If the same checks are used in many places in the program, defining names for the value checker will be the better choice since -it improves maintainability. For seldomly used kind of checks, the +it improves maintainability. For seldom used kind of checks, the parameterized value checkers might be more convenient. ==== Multiplicity