feat: add links to next section

docs/phase0.md

@@ -2,4 +2,6 @@
 
 Parse arguments, apply any special cases from arguments such as updating the repo using git, cleaning cache from old builds for a full rebuild, etc.
 
-Once this phase is over our dependencies are available, arguments parsed and ready to start the next phase
+Once this phase is over our dependencies are available, arguments parsed and ready to start the next phase.
+
+And now, [phase1](./phase1.md)

docs/phase1.md

@@ -14,4 +14,6 @@ It also generates the paths for global texts files, for storing commonly used st
 
 It does a few other things, as well, for an exhaustive list please examine the codebase.
 
-After phase 1 is complete we can be reasonably sure that dependencies for phase 2 etc are in place, and with timestamps that phase2 can depend on to be useful
+After phase 1 is complete we can be reasonably sure that dependencies for phase 2 etc are in place, and with timestamps that phase2 can depend on to be useful.
+
+And now, [phase2](./phase2.md)

docs/phase2.md

@@ -15,3 +15,5 @@ It will
 9. Copies over any static files that are needed, like images, PDFs etc.
 
 After phase 2 is over we have a copy of all sites built. If the site was not staged then it is in the target directory if it was staged, then it is in the staging directory.
+
+And now, [phase3](./phase3.md)

docs/phase3.md

@@ -5,3 +5,5 @@ This final phase relates to finishing up the build
 If the build was staged then this is the phase where the built result gets copied to the target(s).
 
 And if specified the resulting build is served over localhost for rapid debugging.
+
+And finished!