diff --git a/source/modify-hello-flake.adoc0 b/source/modify-hello-flake.adoc0
index 1282de9..f78b5fb 100644
--- a/source/modify-hello-flake.adoc0
+++ b/source/modify-hello-flake.adoc0
@@ -5,9 +5,14 @@ opportunity to check your understanding of flakes.
 
 The first step is to enter a development shell.
 
+////
+The user would have done this in an earlier section.
+However, my adoc0 scripts clean up after themselves, so we need to do it again.
+$ git clone https://codeberg.org/mhwombat/hello-flake
+$ cd hello-flake
+////
+
 ....
-$# git clone https://codeberg.org/mhwombat/hello-flake
-$# cd hello-flake
 $ nix develop
 ....
 
diff --git a/source/python-flake.adoc0 b/source/python-flake.adoc0
index 569ad5f..84581ef 100644
--- a/source/python-flake.adoc0
+++ b/source/python-flake.adoc0
@@ -177,8 +177,8 @@ You can test that your package is properly configured by going to
 another directory and running it from there.
 
 ....
-$ cd ~
-$ nix run ~/tutorial-practice/hello-python
+$ cd ..
+$ nix run ./hello-python
 ....
 
 If you move the project to a public repo, anyone can run it. Recall from
@@ -194,5 +194,5 @@ Python flake.
 
 ////
 Good adoc0 scripts clean up after themselves.
-$ cd .. ; rm -rf hello-python # clean up
+$ rm -rf hello-python # clean up
 ////