Fix error

Author: gloridelmorales

release-notes/2025/includes/boards/sprint-260-update.md

@@ -14,18 +14,18 @@ Azure Boards and Azure Pipelines now supports integration with GitHub Enterprise
 Create a new connection in Azure Boards. Then select the **GitHub Enterprise Cloud with data residency** option.
 
 > [!div class="mx-imgBorder"]
-> ![Image to show Connect GitHub with Azure Boards.](../../media/260-boards-01.gif "Image to show Connect GitHub with Azure Boards.")
+> ![Image to show Connect GitHub with Azure Boards.](../../media/260-boards-01.png "Image to show Connect GitHub with Azure Boards.")
 
 * To connect an Azure Pipeline:
 
 Create a new Pipeline and select GitHub > More Options > GitHub Enterprise Cloud with data residency.
 
 > [!div class="mx-imgBorder"]
-> ![Image to show GitHub Enterprise with data residency screen.](../../media/260-boards-02.gif "Image to show GitHub Enterprise with data residency screen.")
+> ![Image to show GitHub Enterprise with data residency screen.](../../media/260-boards-02.png "Image to show GitHub Enterprise with data residency screen.")
 
 Then enter the URL of your GitHub Enterprise Cloud organization.
 
 > [!div class="mx-imgBorder"]
-> ![Image to show GitHub Enterprise with data residency.](../../media/260-boards-03.gif "Image to show GitHub Enterprise with data residency.")
+> ![Image to show GitHub Enterprise with data residency.](../../media/260-boards-03.png "Image to show GitHub Enterprise with data residency.")
 
 After your https://organization.ghe.com url is validated, the experience is same as it has always been, and you can select your GitHub repositories.

…tes/2025/repos/sprint-259-update copy.md …se-notes/2025/repos/sprint-260-update.mdrelease-notes/2025/repos/sprint-259-update copy.md renamed to release-notes/2025/repos/sprint-260-update.md release-notes/2025/repos/sprint-259-update copy.md renamed to release-notes/2025/repos/sprint-260-update.md

@@ -22,7 +22,7 @@ Check out the release notes for details.
 
 ### Azure Repos
 
-[!INCLUDE [sprint-260-update-links](includes/pipelines/sprint-260-update-links.md)]
+[!INCLUDE [sprint-260-update-links](includes/repos/sprint-260-update-links.md)]
 
 ## General
 

release-notes/2025/sprint-260-update.md

@@ -272,7 +272,7 @@ These investments include:
 
 Managed DevOps Pools is an evolution of Azure DevOps Virtual Machine Scale Set agent pools. It provides better pool scalability and reliability, simplifies pool management, and allows you to use the VM images from Microsoft-hosted agents on custom Azure VMs. You can read more about Managed DevOps Pools [here](https://aka.ms/mdp-docs). Features to support new scenarios will be added to Managed DevOps Pools and not Virtual Machine Scale Set pools. Managed DevOps Pools is generally available, so you can migrate your Virtual Machine Scale Set pools to Managed DevOps Pools and use them for production workflows, wherever possible.
 
-You will find the detailed roadmap [here](https://learn.microsoft.com/en-us/azure/devops/managed-devops-pools/features-timeline?view=azure-devops)
+You will find the detailed roadmap [here](/azure/devops/managed-devops-pools/features-timeline?view=azure-devops)
 
 ### YAML and release pipelines feature parity