Updated order so forecast is 3rd

travis/2-audit.md

@@ -318,4 +318,4 @@ Each pipeline will have a variety of files written that include:
 
 ### Next lab
 
-[Perform a dry-run of a Travis CI pipeline](3-dry-run.md)
+[Forecast potential build runner usage](3-forecast.md)

travis/3-forecast.md

@@ -95,6 +95,6 @@ gh valet forecast --source-file-path tmp/**/jobs/*.json -o tmp/combined-forecast
 
 You can now inspect the output of the command to see a forecast report using all of the files matching the `tmp/**/jobs/*.json` pattern.
 
-## Next steps
+### Next Lab
 
-This concludes all labs for migrating Travis CI pipelines to Actions with Valet!
+[Perform a dry-run of a Travis CI pipeline](4-dry-run.md)

travis/4-dry-run.md

@@ -116,4 +116,4 @@ Despite these two pipelines using different syntax they will function equivalent
 
 ## Next lab
 
-[Use custom transformers to customize Valet's behavior](./4-custom-transformers.md)
+[Use custom transformers to customize Valet's behavior](./5-custom-transformers.md)

travis/6-migrate.md

@@ -46,6 +46,6 @@ Finally, you can merge the pull request once your review has completed. You can
 
 At this point, the migration has completed and you have successfully migrated a Travis CI pipeline to Actions!
 
-### Next Lab
+## Next steps
 
-[Forecast potential build runner usage](6-forecast.md)
+This concludes all labs for migrating Travis CI pipelines to Actions with Valet!