Reorder jenkins labs

jenkins/2-audit.md

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

jenkins/3-forecast.md

@@ -101,4 +101,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 Jenkins pipelines to Actions with Valet!
+[Perform a dry-run migration of a Jenkins pipeline](4-dry-run.md)

jenkins/4-dry-run.md

@@ -141,4 +141,4 @@ Try running the `dry-run` command for different pipelines in the Jenkins server.
 
 ## 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)

jenkins/5-custom-transformers.md

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

jenkins/6-migrate.md

@@ -52,4 +52,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 Jenkins pipelines to Actions with Valet!