Fix warnings

Author: gloridelmorales

release-notes/2025/includes/general/sprint-257-update-links.md

@@ -10,4 +10,4 @@ ms.topic: include
 - [Removal of expired Azure DevOps OAuth Apps](#removal-of-expired-azure-devops-oauth-apps)
 - [Azure DevOps login flow no longer relies on Azure Resource Manager audience](#azure-devops-login-flow-no-longer-relies-on-azure-resource-manager-audience)
 - [New Microsoft Entra OAuth scopes](#new-microsoft-entra-oauth-scopes)
-- [Request Access URL availability](request-access-url-availability)
+- [Request Access URL availability](#request-access-url-availability)

release-notes/2025/includes/pipelines/sprint-257-update-links.md

@@ -5,7 +5,7 @@ ms.date: 6/16/2025
 ms.topic: include
 ---
 
-- [Managed DevOps Pools - Image Deprecations](manged-devops-pools-image-deprecations)
+- [Managed DevOps Pools - Image Deprecations](#manged-devops-pools-image-deprecations)
 - [New Triggers page](#new-triggers-page)
 - [StringList parameter type](#stringlist-parameter-type)
 - [See the full YAML code of a pipeline run](#see-the-full-yaml-code-of-a-pipeline-run)

release-notes/2025/includes/pipelines/sprint-257-update.md

@@ -16,7 +16,7 @@ YAML pipelines provide you multiple powerful options to define when your pipelin
 This sprint, were introducing a **Triggers** page that gives you an overview of what triggers you have defined in your pipeline.
 
 > [!div class="mx-imgBorder"]
-> [![Screenshot of Pipelines Triggers.](../../media/257-pipelines-01.png "Screenshot of Pipelines Triggers.")](../../media/257-pipelines-01.png#lightbox)
+> [![Screenshot of Pipelines Triggers.](../../media/257-pipelines-01.png "Screenshot of Pipelines Triggers page.")](../../media/257-pipelines-01.png#lightbox)
 
 Imagine you have the following YAML pipeline defined in the `main` branch of a repo. Consider there's also a `feature` branch that has the same YAML pipeline code.
 
@@ -42,7 +42,7 @@ resources:
 When you navigate to the **Triggers** page, you see the following
 
 > [!div class="mx-imgBorder"]
-> [![Screenshot of Continuous integration triggers.](../../media/257-pipelines-02.png "Screenshot of Continuous integration triggers.")](../../media/257-pipelines-02.png#lightbox)
+> [![Screenshot of Continuous integration triggers.](../../media/257-pipelines-02.png "Screenshot of triggers page select branch with default branch main.")](../../media/257-pipelines-02.png#lightbox)
 
 Notice the default branch of the pipeline, `main`, is preselected. 
 
@@ -51,12 +51,12 @@ You see there is a _Continuous integration trigger_ for this branch, and it's de
 When you navigate to the _Schedule triggers_, you see there are triggers defined, and you can see their details.
 
 > [!div class="mx-imgBorder"]
-> [![Screenshot of Pipelines schedule triggers.](../../media/257-pipelines-03.png "Screenshot of Pipelines schedule triggers.")](../../media/257-pipelines-03.png#lightbox)
+> [![Screenshot of Pipelines schedule triggers.](../../media/257-pipelines-03.png "Screenshot of Pipelines schedule triggers details.")](../../media/257-pipelines-03.png#lightbox)
 
 When you navigate to the _Resource triggers_ section, you see the defined resource triggers and their details.
 
 > [!div class="mx-imgBorder"]
-> [![Screenshot of Pipelines resource triggers.](../../media/257-pipelines-04.png "Screenshot of Pipelines resource triggers.")](../../media/257-pipelines-04.png#lightbox)
+> [![Screenshot of Pipelines resource triggers.](../../media/257-pipelines-04.png "Screenshot of Pipelines resource triggers section.")](../../media/257-pipelines-04.png#lightbox)
 
 You can switch branches, from `main` to `feature`, to see what triggers you defined for the `feature` branch.