remove message

010-AzureDevOps/Student/Guides/challenge05.md

@@ -24,6 +24,7 @@ In Azure DevOps we use Azure Pipelines to automate our build process. For our ap
 4. You can delete the `publish the artifact` step since we are going to create a container and publish it to Azure Container Registry.
 5. Now that our .NET core application is compiled and all the unit tests have been run, we need to package it into a Docker Container and publish the container to Azure Container Registry, to do this we are going to add a docker task to our build pipeline.
    1. We want to use the `buildAndPush` command with the following Docker file `**/Dockerfile`, build context `$(System.DefaultWorkingDirectory)/PublishedWebApp` and tag `$(Build.BuildId)` (NOTE: here we are dynamically pulling the build number from Azure DevOps at run time)
+   2. Next we need to connect it to the container registry and repository (i.e. `<prefix>devopsimage`) that we setup in our infrastructure as code challenge.
 6. Lets kick off a build manually to ensure that we have a working build.
 7. Next lets notify the team if the build breaks by creating a new Work Item. ([Hint](https://docs.microsoft.com/en-us/azure/devops/pipelines/build/options?view=azure-devops&tabs=designer#create-a-work-item-on-failure))
 8.  Now, make and check in a code change that will break the build. Ensure that a work item gets created. 
@@ -35,6 +36,4 @@ In Azure DevOps we use Azure Pipelines to automate our build process. For our ap
 2. Review the test results generated by your build. HINT: look in the logs from your build to find where the test run was published. 
 3. Using the Azure Portal or CLI you should see your container in your Azure Container Registry Repository
 
-> NOTE: We are just scratching the surface of what is offered in Azure for Infrastructure as Code, if you are interested in learning more there is a full What the Hack focused on Azure Infrastructure as Code.
-
 [Back](challenge04.md) - [Home](../../readme.md) - [Next](challenge06.md)