Skip to content

Conversation

@changeworld
Copy link
Contributor

Azure container registry -> Azure Container Registry

Azure container registry -> Azure Container Registry
@prmerger-automator
Copy link
Contributor

@changeworld : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit dffbb67:

✅ Validation status: passed

File Status Preview URL Details
docs/azure/azure-deployment-using-github-actions.md ✅Succeeded
docs/azure/end-to-end-deployment-entity-framework-core-github-actions.md ✅Succeeded
docs/containers/container-tools-react.md ✅Succeeded
docs/containers/container-tools.md ✅Succeeded
docs/containers/hosting-web-apps-in-docker.md ✅Succeeded
docs/containers/includes/vs-2019/container-tools.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@ttorble
Copy link
Contributor

ttorble commented Apr 22, 2025

@ghogen and @alexwolfmsft

Can you review the proposed changes? Note that the style guide says: "Lowercase when referring to an instance of using the service: container registry."

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Apr 22, 2025
@v-dirichards
Copy link
Contributor

@ghogen I'll merge this PR based on your approval. If this article requires further changes, please open a separate pull request.

@v-dirichards v-dirichards merged commit 7950166 into MicrosoftDocs:main Apr 22, 2025
2 checks passed
@changeworld changeworld deleted the patch-1 branch April 22, 2025 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants