Reorder the migrate and forecast labs

jenkins/4-custom-transformers.md

@@ -318,4 +318,4 @@ Thats it! Congratulations you have overridden Valet's default behavior by custom
 
 ## Next lab
 
-[Forecast Jenkins Usage](../jenkins/5-forecast.md#forecast-the-runner-usage-of-a-jenkins-instance)
+[Perform a production migration of a Jenkins pipeline](5-migrate.md)

jenkins/readme.md

@@ -58,8 +58,8 @@ Perform the following labs to test-drive Valet
 2. [Perform an audit of a Jenkins server](2-audit.md)
 3. [Perform a dry-run of a Jenkins pipeline](3-dry-run.md)
 4. [Use custom transformers to customize Valet's behavior](4-custom-transformers.md)
-5. [Forecast potential build runner usage](5-forecast.md)
-6. [Perform a production migration of a Jenkins pipeline](6-migrate.md)
+5. [Perform a production migration of a Jenkins pipeline](5-migrate.md)
+6. [Forecast potential build runner usage](6-forecast.md)
 
 ## Troubleshoot the Valet CLI