diff --git a/docs/extend/develop/samples-overview.md b/docs/extend/develop/samples-overview.md index 89a2aa32d75..e69d029fd7d 100644 --- a/docs/extend/develop/samples-overview.md +++ b/docs/extend/develop/samples-overview.md @@ -49,7 +49,7 @@ Other open source examples that you might be interested in. | [Retrospectives](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.team-retrospectives) | [GitHub](https://github.com/microsoft/vsts-extension-retrospectives) | Hub | First-class experience for retrospectives and general feedback board scenarios. Collect feedback on your project milestones, organize and prioritize, and create and track actionable tasks, which can help your team improve over time. | | [Estimate](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.estimate) | [GitHub](https://github.com/microsoft/azure-boards-estimate) | Hub, Work item action menu| Play Planning Poker in Azure DevOps. Select work from an iteration, query, or your backlog, estimate the effort of those items with your team, and immediately update the work items. | | [Multivalue control](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.vsts-extensions-multivalue-control) | [GitHub](https://github.com/Microsoft/vsts-extension-multivalue-control) | Work item form | A work item form control, which allows selection of multiple values. | -| [Azure DevOps Extension Tasks](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.vsts-developer-tools-build-tasks) | [GitHub](https://github.com/Microsoft/azure-devops-extension-tasks) | Build and release tasks | Azure Pipelines tasks for packaging and publishing Azure Devops and Visual Studio extensions to the Visual Studio Marketplace. | +| [Azure DevOps Extension Tasks](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.vsts-developer-tools-build-tasks) | [GitHub](https://github.com/Microsoft/azure-devops-extension-tasks) | Build and release tasks | Azure Pipelines tasks for packaging and publishing Azure DevOps and Visual Studio extensions to the Visual Studio Marketplace. | ## Get started diff --git a/docs/organizations/accounts/faq-configure-customize-organization.yml b/docs/organizations/accounts/faq-configure-customize-organization.yml index 88b0d86eee3..12fe7cc3724 100644 --- a/docs/organizations/accounts/faq-configure-customize-organization.yml +++ b/docs/organizations/accounts/faq-configure-customize-organization.yml @@ -79,7 +79,7 @@ sections: For more information, see [Plan your Azure DevOps organization structure](../../user-guide/plan-your-azure-devops-org-structure.md?view=azure-devops). - question: | - Q: Is localization supported in the Azure Devops service? + Q: Is localization supported in the Azure DevOps service? answer: | A: Sorry, we don't support localization in the Azure DevOps service. We do support localization in the on-premises version of Azure DevOps. diff --git a/docs/organizations/security/set-object-level-permissions.md b/docs/organizations/security/set-object-level-permissions.md index 269dcb28df3..778dedc3b32 100644 --- a/docs/organizations/security/set-object-level-permissions.md +++ b/docs/organizations/security/set-object-level-permissions.md @@ -15,7 +15,7 @@ ms.date: 07/15/2024 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)] -As you manage security for your organization, you can set permissions at the organization/collection-level, project-level, and object-level. This article helps you go to the security dialogs for setting permissions at the object-level, as the user interface varies somewhat across Azure Devops. For more information, see [Get started with permissions, access, and security groups](about-permissions.md#permissions). +As you manage security for your organization, you can set permissions at the organization/collection-level, project-level, and object-level. This article helps you go to the security dialogs for setting permissions at the object-level, as the user interface varies somewhat across Azure DevOps. For more information, see [Get started with permissions, access, and security groups](about-permissions.md#permissions). The following items are considered objects: diff --git a/docs/organizations/settings/manage-banners.md b/docs/organizations/settings/manage-banners.md index eac2a5e05fb..c225578cfa8 100644 --- a/docs/organizations/settings/manage-banners.md +++ b/docs/organizations/settings/manage-banners.md @@ -11,7 +11,7 @@ monikerRange: "<=azure-devops" ms.date: 09/11/2024 --- -# Add and manage information banners in Azure Devops +# Add and manage information banners in Azure DevOps [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)] diff --git a/docs/pipelines/agents/certificate.md b/docs/pipelines/agents/certificate.md index 140038dc65c..8be0225ed7d 100644 --- a/docs/pipelines/agents/certificate.md +++ b/docs/pipelines/agents/certificate.md @@ -29,7 +29,7 @@ The agent diagnostic log shows: [2017-11-06 20:55:33Z ERR AgentServer] System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.Http.WinHttpException: A security error occurred ``` -The previous security error might indicate that the build machine doesn't trust the server certificate that you used on your Azure Devops Server host machine. Make sure that you install your self-signed SSL server certificate into the OS certificate store. +The previous security error might indicate that the build machine doesn't trust the server certificate that you used on your Azure DevOps Server host machine. Make sure that you install your self-signed SSL server certificate into the OS certificate store. ``` Windows: Windows certificate store diff --git a/docs/pipelines/release/key-vault-access.md b/docs/pipelines/release/key-vault-access.md index 6570c8f4dc5..241281f634f 100644 --- a/docs/pipelines/release/key-vault-access.md +++ b/docs/pipelines/release/key-vault-access.md @@ -131,7 +131,7 @@ Start by creating a new service principal, this will enable you to access Azure ::: zone pivot="access-from-azure-devops" -## Access a private key vault from Azure Devops +## Access a private key vault from Azure DevOps In this section, we'll explore two methods for accessing a private key vault from Azure DevOps. First, we'll use Variable Groups to link and map secrets from our key vault, followed by setting up inbound access by allowing static IP ranges. We establish inbound access because Azure Pipelines uses the posted Azure DevOps Public IP when querying the Azure Key Vault from a Variable Group. Therefore, by adding inbound connections to the Azure Key Vault firewall, we can successfully connect to our Azure Key Vault. diff --git a/docs/pipelines/repos/includes/bb-limitations.md b/docs/pipelines/repos/includes/bb-limitations.md index 6deb12081e4..c70265a324a 100644 --- a/docs/pipelines/repos/includes/bb-limitations.md +++ b/docs/pipelines/repos/includes/bb-limitations.md @@ -3,4 +3,4 @@ ms.topic: include ms.date: 10/27/2023 --- -Azure Pipelines loads a maximum of 2000 branches from a repository into dropdown lists in the Azure Devops Portal, for example into the **Default branch for manual and scheduled builds** setting, or when choosing a branch when running a pipeline manually. If you don't see your desired branch in the list, type the desired branch name manually. +Azure Pipelines loads a maximum of 2000 branches from a repository into dropdown lists in the Azure DevOps Portal, for example into the **Default branch for manual and scheduled builds** setting, or when choosing a branch when running a pipeline manually. If you don't see your desired branch in the list, type the desired branch name manually. diff --git a/docs/project/work-across-projects-faqs.yml b/docs/project/work-across-projects-faqs.yml index 993cb39cf05..7c96063ec3c 100644 --- a/docs/project/work-across-projects-faqs.yml +++ b/docs/project/work-across-projects-faqs.yml @@ -99,7 +99,7 @@ sections: - question: Can I perform capacity planning across projects? answer: | - **No**. Azure Devops doesn't store capacity planning data in the work tracking data store or Analytics service, as it isn't a supported feature. + **No**. Azure DevOps doesn't store capacity planning data in the work tracking data store or Analytics service, as it isn't a supported feature. - question: How do I manage dependencies across projects? answer: | diff --git a/docs/repos/git/pull-request-targets.md b/docs/repos/git/pull-request-targets.md index f8b260527e1..7db9102417d 100644 --- a/docs/repos/git/pull-request-targets.md +++ b/docs/repos/git/pull-request-targets.md @@ -158,7 +158,7 @@ first parent history still demonstrates a preference for `feature/targets`. ### Breaking Ties If two branches have the same first-parent history intersection, then -Azure Devops selects the branch that appears earlier in the +Azure DevOps selects the branch that appears earlier in the `pull_request_targets` list. If multiple branches are still tied based on the `pull_request_targets` list due to a prefix match, then the earliest in alphabetical order wins. diff --git a/docs/repos/tfvc/destroy-command-team-foundation-version-control.md b/docs/repos/tfvc/destroy-command-team-foundation-version-control.md index f35a1ad4d2d..7f68f74073d 100644 --- a/docs/repos/tfvc/destroy-command-team-foundation-version-control.md +++ b/docs/repos/tfvc/destroy-command-team-foundation-version-control.md @@ -18,7 +18,7 @@ ms.subservice: azure-devops-repos-tfvc Use the `tf destroy` command to destroy, or permanently delete, version-controlled files from Team Foundation Version Control (TFVC). > [!NOTE] -> Deleting a TFVC repository inside Azure Devops is not allowed once it has been created. The command `tf destroy` will only destroy, or permanently delete, version-controlled files or folders but will not delete the TFVC repository. It will still appear in the list of options with the message deleted. +> Deleting a TFVC repository inside Azure DevOps is not allowed once it has been created. The command `tf destroy` will only destroy, or permanently delete, version-controlled files or folders but will not delete the TFVC repository. It will still appear in the list of options with the message deleted. Sometimes you have to clean up version control systems. For example, if some files are infected with a computer virus, you have to remove them permanently from version control. Don't destroy files that are still needed. The destroy action can't be reversed.