Update links

circle_ci/2-audit.md

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

circle_ci/3-forecast.md

@@ -96,4 +96,4 @@ You can now inspect the output of the command to see a forecast report using all
 
 ## Next steps
 
-This concludes all labs for migrating CircleCI pipelines to Actions with Valet!
+[Perform a dry-run of a CircleCI pipeline](4-dry-run.md)

circle_ci/4-dry-run.md

@@ -184,10 +184,11 @@ jobs:
     - run: bundle exec rspec spec --profile 10 --format RspecJunitFormatter --out /tmp/test-results/rspec/results.xml --format progress
     - run: bundle exec rubocop --format progress
 ```
+
 </details>
 
 Despite these two pipelines using different syntax they will function equivalently.
 
 ## 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)

circle_ci/5-custom-transformers.md

@@ -195,4 +195,4 @@ That's it! Congratulations, you have overridden Valet's default behavior by cust
 
 ## Next lab
 
-[Perform a production migration of a CircleCI pipeline](5-migrate.md)
+[Perform a production migration of a CircleCI pipeline](6-migrate.md)

circle_ci/6-migrate.md

@@ -48,4 +48,4 @@ At this point, the migration has completed and you have successfully migrated a
 
 ### Next Lab
 
-[Forecast potential build runner usage](6-forecast.md)
+This concludes all labs for migrating CircleCI pipelines to Actions with Valet!