move update under Repos vs. General

Author: ncouraud

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

@@ -6,5 +6,4 @@ ms.topic: include
 ---
 
 - [Only organizations with existing public projects can create new ones](#only-organizations-with-existing-public-projects-can-create-new-ones)
-- [Azure DevOps login flow no longer relies on Azure Resource Manager audience](#azure-devops-login-flow-no-longer-relies-on-azure-resource-manager-audience)
-- [Azure DevOps remote index support in VSCode](#azure-devops-remote-index-support-in-vscode)
+- [Azure DevOps login flow no longer relies on Azure Resource Manager audience](#azure-devops-login-flow-no-longer-relies-on-azure-resource-manager-audience)

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

@@ -20,10 +20,4 @@ Due to Azure DevOps previous reliance on ARM, admins had to permit all Azure Dev
 There remain a couple of notable exceptions  — the following ​user groups may need continued access to ARM:
 
 1. Billing admins need access to ARM to setup billing and access subscriptions
-2. Service Connection creators require continued access to ARM for ARM role assignment and updates to MSIs
-
-### Azure DevOps remote index support
-
-Azure DevOps now supports remote indexes for IDE workspaces that are linked to Azure DevOps repos. This enables #codebase to search for relevant snippets almost instantly without any initialization. This even works for larger repos with tens of thousands of indexable files. Support for remote workspaces has released starting with the July updates to Visual Studio  and VS Code. For more info please see the [VS Code Release Notes](https://code.visualstudio.com/updates/v1_103#_azure-devops-repos-remote-index-support). 
-
-Remote indexes are used automatically when working in a workspace that is linked to Azure DevOps through git. Make sure you are also logged into Visual Studio or VS Code  with the Microsoft account you use to access the Azure DevOps repo.
+2. Service Connection creators require continued access to ARM for ARM role assignment and updates to MSIs

release-notes/2025/includes/repos/sprint-260-update-links.md

@@ -5,4 +5,5 @@ ms.date: 8/11/2025
 ms.topic: include
 ---
 
-- [Improved screen reader support for pull request experience](#improved-screen-reader-support-for-pull-request-experience)
+- [Improved screen reader support for pull request experience](#improved-screen-reader-support-for-pull-request-experience)
+- [Azure DevOps remote index support in VSCode](#azure-devops-remote-index-support-in-vscode)

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

@@ -23,4 +23,10 @@ Then, click on the **Editor preferences** button.
 On the popup menu, select the **Enable announcements for line changes and comments to enhance screen reader accessibility** option and **Save**.
 
 > [!div class="mx-imgBorder"]
-> [![Image to Editor preferences.](../../media/260-repos-03.png "Image to Editor preferences.")](../../media/260-repos-03.png#lightbox)
+> [![Image to Editor preferences.](../../media/260-repos-03.png "Image to Editor preferences.")](../../media/260-repos-03.png#lightbox)
+
+### Azure DevOps remote index support
+
+Azure DevOps now supports remote indexes for IDE workspaces that are linked to Azure DevOps repos. This enables #codebase to search for relevant snippets almost instantly without any initialization. This even works for larger repos with tens of thousands of indexable files. Support for remote workspaces has released starting with the July updates to Visual Studio  and VS Code. For more info please see the [VS Code Release Notes](https://code.visualstudio.com/updates/v1_103#_azure-devops-repos-remote-index-support). 
+
+Remote indexes are used automatically when working in a workspace that is linked to Azure DevOps through git. Make sure you are also logged into Visual Studio or VS Code  with the Microsoft account you use to access the Azure DevOps repo.