Add missing instruction to move to the next exercise (#127)

eloots · web-flow · commit 0a58fae7e566 · 2023-09-07T16:30:16.000+02:00
diff --git a/exercises/exercise_001_dotty_deprecated_syntax_rewriting/README.md b/exercises/exercise_001_dotty_deprecated_syntax_rewriting/README.md
@@ -155,7 +155,10 @@ wildcard import syntax from using an asterix (`*`) instead of an underscore (`_`
 $ git commit -a -m "Snapshot after Scala 3 compiler syntax rewrites"
 ```
 
-- Move to the next exercise by running the `cmtc next-exercise` command from the command line.
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
 
 > NOTE: The extra bit of code that was added via `cmtc pull-template ...` can either be left as-is
 >  or be removed. Your choice.
diff --git a/exercises/exercise_002_dotty_new_syntax_and_indentation_based_syntax/README.md b/exercises/exercise_002_dotty_new_syntax_and_indentation_based_syntax/README.md
@@ -72,8 +72,10 @@ documentation.
 $ git commit -a -m "Snapshot after Scala 3 compiler syntax rewrites"
 ```
 
-- You've just completed this exercise. Let's move on to the next exercise by
-  executing the `cmtc next-exercise` command.
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
 
 ## Source code formatting & Markdown viewer in IntelliJ
 
diff --git a/exercises/exercise_003_top_level_definitions/README.md b/exercises/exercise_003_top_level_definitions/README.md
@@ -55,6 +55,11 @@ Let's continue with the core topic of this exercise:
 
 - Verify that the application runs correctly
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_004_parameter_untupling/README.md b/exercises/exercise_004_parameter_untupling/README.md
@@ -57,6 +57,11 @@ pairs.map(_ + _)
 
 - Verify that the application runs correctly
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_005_extension_methods/README.md b/exercises/exercise_005_extension_methods/README.md
@@ -75,6 +75,11 @@ part of this exercise (adding the new extension methods).
 
 - Verify that the application runs correctly.
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_006_using_and_summon/README.md b/exercises/exercise_006_using_and_summon/README.md
@@ -29,6 +29,11 @@ use of _scala 2_'s `implicit`s and `implicitly`.
 
 - Verify that the application runs correctly
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_007_givens/README.md b/exercises/exercise_007_givens/README.md
@@ -33,6 +33,11 @@ secondly because these names don't really have a useful application in most case
 
 - Verify that the application runs correctly.
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_008_enum_and_export/README.md b/exercises/exercise_008_enum_and_export/README.md
@@ -77,6 +77,11 @@ in this exercise.
 
 - Verify that the application runs correctly.
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_009_union_types/README.md b/exercises/exercise_009_union_types/README.md
@@ -69,6 +69,11 @@ Which of these actors receive messages that are responses from other actors?
 
 - Verify that the application runs correctly
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_010_exploring_opaque_type_aliases/README.md b/exercises/exercise_010_exploring_opaque_type_aliases/README.md
@@ -43,3 +43,9 @@ We will now walk through the different features
 ### Opaque type aliases
 
 - Repeat the same steps for file `UsingTheAliases.scala` in the `opaquetypelaliases.opaquetypealias`
+
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
diff --git a/exercises/exercise_011_optional_opaque_type_aliases/README.md b/exercises/exercise_011_optional_opaque_type_aliases/README.md
@@ -1,5 +1,9 @@
 # Opaque Type Aliases
 
+> NOTE: this exercise is optional. It's purpose is to show that certain use
+>       cases of opaque type aliases sound great at first, but turn out
+>       to be very difficult to implement
+
 ## Background
 
 An Opaque Type Alias can be used to provide the functionality of a "wrapper
@@ -105,6 +109,11 @@ There are more type aliases in the source code that potentially could be convert
 opaque versions. One that sticks out is the `Sudoku` type alias
 (`type Sudoku = Vector[ReductionSet`). You may want to take a stab at converting it...
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_012_multiversal_equality/README.md b/exercises/exercise_012_multiversal_equality/README.md
@@ -38,6 +38,11 @@ error.
 - Run the provided tests by executing the `test` command from the `sbt` prompt
   and verify that all tests pass
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_020_opaque_type_aliases_alt/README.md b/exercises/exercise_020_opaque_type_aliases_alt/README.md
@@ -1,5 +1,9 @@
 # Opaque Type Aliases
 
+> NOTE: this exercise is optional. It's purpose is to show that certain use
+>       cases of opaque type aliases sound great at first, but turn out
+>       to be very difficult to implement
+
 ## Background
 
 An Opaque Type Alias can be used to provide the functionality of a "wrapper
@@ -68,6 +72,11 @@ this exercise. Specifically we will convert the last of these type aliases,
 
 - Verify that the application runs correctly
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
diff --git a/exercises/exercise_021_multiversal_equality/README.md b/exercises/exercise_021_multiversal_equality/README.md
@@ -38,6 +38,11 @@ error.
 - Run the provided tests by executing the `test` command from the `sbt` prompt
   and verify that all tests pass
 
+### Next steps
+
+After successfully completing the tasks in this exercise, move to the next one by
+running the `cmtc next-exercise` from the command line.
+
 ## Source code formatting & Markdown viewer in IntelliJ
 
 ### Source code formatting
