reorder azdo labs

azure_devops/2-audit.md

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

azure_devops/3-forecast.md

@@ -101,4 +101,4 @@ Additionally, these metrics are defined for each queue of runners defined in Azu
 
 ## Next steps
 
-This concludes all labs for migrating Azure DevOps pipelines to Actions with Valet!
+[Perform a dry-run migration of an Azure DevOps pipeline](4-dry-run.md)

azure_devops/4-dry-run.md

@@ -90,4 +90,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)

azure_devops/5-custom-transformers.md

@@ -232,4 +232,4 @@ That's it! At this point you have overridden Valet's default behavior by customi
 
 ## Next lab
 
-[Perform a production migration of an Azure DevOps pipeline](5-migrate.md)
+[Perform a production migration of an Azure DevOps pipeline](6-migrate.md)

azure_devops/6-migrate.md

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