update + build err

Author: Rami Bououni

docs/pipelines/get-started/pipelines-get-started.md

@@ -49,7 +49,7 @@ For instructions, see [build](../build/ci-build-git.md) and [deploy](../release/
 |-------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------|------------------|-----------------|
 | **Agents**                        | A software component that runs on a virtual machine or a physical machine and is responsible for executing the tasks defined in your Azure Pipelines.                                      |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../agents/agents.md)   |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../agents/agents.md)       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../agents/agents.md)        |
 | **Approvals**            | Control your deployment workflow by requiring designated approvers to approve before deploying to a stage.                  |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/approvals.md#approvals)  |       :::image type="icon" source="../../media/icons/delete-icon.png" border="false":::       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../release/approvals/approvals.md#predeployment-approvals)        |
-| **Artifacts**      | Download and publish your binaries and various types of packages to different destinations.          |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../artifacts/pipeline-artifacts.md?&tabs=yaml-task)  |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../artifacts/pipeline-artifacts.md?&tabs=yaml-task)       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../release/deploy-multiple-branches.md#create-a-release-pipeline)          |
+| **Artifacts**      | Download and publish your binaries and various types of packages to different destinations.          |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../artifacts/pipeline-artifacts.md?&tabs=yaml-task)  |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../artifacts/pipeline-artifacts.md?&tabs=yaml-task)       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../release/deploy-multiple-branches.md#create-a-classic-release-pipeline)          |
 | **Caching**                     | Reduce build time by caching and reusing dependencies from previous runs. |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../release/caching.md)   |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../release/caching.md)       |        :::image type="icon" source="../../media/icons/delete-icon.png" border="false":::         | 
 | **Conditions**               | Specify conditions under which a step, job, or stage should run.                                         |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/conditions.md?tabs=yaml)    |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/conditions.md?tabs=classic)       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/conditions.md?tabs=classic)        |
 | **Container jobs**      | Specify jobs to run in a container.                                                          |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/container-phases.md)  |       :::image type="icon" source="../../media/icons/delete-icon.png" border="false":::       |        :::image type="icon" source="../../media/icons/delete-icon.png" border="false":::        |
@@ -78,7 +78,7 @@ For instructions, see [build](../build/ci-build-git.md) and [deploy](../release/
 |-------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------|------------------|-----------------|
 | **Agents**                        | A software component that runs on a virtual machine or a physical machine and is responsible for executing the tasks defined in your Azure Pipelines.                                      |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../agents/agents.md)   |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../agents/agents.md)       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../agents/agents.md)        |
 | **Approvals**            | Control your deployment workflow by requiring designated approvers to approve before deploying to a stage.                  |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/approvals.md#approvals)  |       :::image type="icon" source="../../media/icons/delete-icon.png" border="false":::       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../release/approvals/approvals.md#predeployment-approvals)        |
-| **Artifacts**      | Download and publish your binaries and various types of packages to different destinations.          |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../artifacts/pipeline-artifacts.md?&tabs=yaml-task)  |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../artifacts/pipeline-artifacts.md?&tabs=yaml-task)       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../release/deploy-multiple-branches.md#create-a-release-pipeline)          |
+| **Artifacts**      | Download and publish your binaries and various types of packages to different destinations.          |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../artifacts/pipeline-artifacts.md?&tabs=yaml-task)  |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../artifacts/pipeline-artifacts.md?&tabs=yaml-task)       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../release/deploy-multiple-branches.md#create-a-classic-release-pipeline)          |
 | **Conditions**               | Specify conditions under which a step, job, or stage should run.                                         |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/conditions.md?tabs=yaml)    |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/conditions.md?tabs=classic)       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/conditions.md?tabs=classic)        |
 | **Container jobs**      | Specify jobs to run in a container.                                                          |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../process/container-phases.md)  |       :::image type="icon" source="../../media/icons/delete-icon.png" border="false":::       |        :::image type="icon" source="../../media/icons/delete-icon.png" border="false":::        |
 | **Demands** | Ensure that the capabilities your pipeline needs are present on the running agent.  |  :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../agents/agents.md#configure-demands)  |       :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../agents/agents.md?tabs=classic#configure-demands)       |        :::image type="icon" source="../../media/icons/checkmark.png" border="false"::: [doc](../agents/agents.md?tabs=classic#configure-demands)        |

docs/pipelines/release/deploy-multiple-branches.md

@@ -65,7 +65,7 @@ In this section, you create the base Classic release pipeline and configure the
 
     With this filter in place, the **Dev** stage deploys only when the release is created from a build of the *Dev* branch.
 
-    :::image type="content" source="media/add-predeployment-conditions-to-classic-release.png" alt-text="A screenshot displaying how to set up the pre-deployment conditions in a Classic release pipeline.":::
+    :::image type="content" source="media/configure-pre-deployment-conditions-classic-release-pipeline.png" alt-text="A screenshot displaying how to set up the pre-deployment conditions in a Classic release pipeline.":::
 
 
 ## Add a new stage
@@ -95,7 +95,7 @@ In this section, you add a second stage (**Prod**) to the same release pipeline
 
     With this filter in place, the **Prod** stage deploys only when the release is created from a build of the *main* branch.
 
-    :::image type="content" source="media/add-predeployment-conditions-to-classic-release-prod-stage.png" alt-text="A screenshot displaying how to configure the predeployment conditions for the Prod stage in a Classic release pipeline.":::  
+    :::image type="content" source="media/configure-pre-deployment-conditions-classic-release-production-stage.png" alt-text="A screenshot displaying how to configure pre-deployment conditions for the production stage in a Classic release pipeline.":::  
 
 ## Deploy to a specific stage
 
@@ -115,8 +115,6 @@ At this point, your release pipeline is configured to route deployments by branc
 
 By validating both branch paths, you can confirm that each environment deploys only from the branch intended for that stage.
 
-:::image type="content" source="media/deploy-to-specific-stage.png" alt-text="A screenshot displaying deployment to a specific stage.":::  
-
 ## Related content
 
 - [Create a multi-stage release pipeline](define-multistage-release-process.md)

docs/pipelines/release/deploy-pull-request-builds.md

@@ -19,7 +19,7 @@ Pull requests provide an effective way to review code changes before merging the
 
 | **Product**        | **Requirements**    |
 |--------------------|---------------------|
-| **Azure DevOps**   | - An [Azure DevOps project](../../organizations/projects/create-project.md).<br> - Source code hosted on Azure Repos or GitHub. If you don’t have a repository, you can use the [pipelines-dotnet-core](https://github.com/MicrosoftDocs/pipelines-dotnet-core) sample app to create one.<br> - A working [pipeline](../create-first-pipeline.md) for your repository.<br> - A Classic release pipeline. If you don't have one, [set up a Classic release pipeline](./deploy-multiple-branches.md#create-a-release-pipeline). |
+| **Azure DevOps**   | - An [Azure DevOps project](../../organizations/projects/create-project.md).<br> - Source code hosted on Azure Repos or GitHub. If you don’t have a repository, you can use the [pipelines-dotnet-core](https://github.com/MicrosoftDocs/pipelines-dotnet-core) sample app to create one.<br> - A working [pipeline](../create-first-pipeline.md) for your repository.<br> - A Classic release pipeline. If you don't have one, [set up a Classic release pipeline](./deploy-multiple-branches.md#create-a-classic-release-pipeline). |
 
 ## Pull request deployments