diff --git a/handouts/src/25-simulating.md b/handouts/src/25-simulating.md
index 4c123a824bcd585ca6f51681c8dc7ccd2600a64a..19958b83e167243f61eeabf26a598bf2276f8f7c 100644
--- a/handouts/src/25-simulating.md
+++ b/handouts/src/25-simulating.md
@@ -300,16 +300,6 @@ adjust the microbenchmark to evaluate its performance:
 Then run the resulting microbenchmark, and compare the performance
 characteristics of our first GPU version to the optimized CPU version.
 
-Finally, if you are going fast, experiment with different work-group sizes in
-order to study the impact of this tuning parameter on performance. In the
-current setup, you need to...
-
-- Change the work-group size declaration in the GLSL compute shader.
-- Change the matching CPU-side declaration in the `gpu::pipeline` module.
-- Recompile the program.
-
-Making this tuning process easier will be the job of specialization constants.
-
 
 ---
 
diff --git a/handouts/src/26-up-to-date.md b/handouts/src/26-up-to-date.md
index d40dab88756da8f523a88d8e4fef9e05bfa1c69c..534c8322ad2b72dc4a52ab337a618752d2475297 100644
--- a/handouts/src/26-up-to-date.md
+++ b/handouts/src/26-up-to-date.md
@@ -91,3 +91,13 @@ number of compute steps per image becomes sufficiently large.
 
 Since the threshold is likely to be hardware-dependent, you will probably want
 to make it configurable via command-line arguments.
+
+Finally, if you are going fast, experiment with different work-group sizes in
+order to study the impact of this tuning parameter on performance. In the
+current setup, you need to...
+
+- Change the work-group size declaration in the GLSL compute shader.
+- Change the matching CPU-side declaration in the `gpu::pipeline` module.
+- Recompile the program.
+
+Making this tuning process easier will be the job of specialization constants.