Fix Visual Studio year in usage-based billing doc (2025 -> 2026) by 812441601 · Pull Request #44898 · github/docs · GitHub
Skip to content

Fix Visual Studio year in usage-based billing doc (2025 -> 2026)#44898

Open
812441601 wants to merge 1 commit into
github:mainfrom
812441601:fix-vs-2026-billing-doc
Open

Fix Visual Studio year in usage-based billing doc (2025 -> 2026)#44898
812441601 wants to merge 1 commit into
github:mainfrom
812441601:fix-vs-2026-billing-doc

Conversation

@812441601

Copy link
Copy Markdown

Summary

This PR fixes an incorrect Visual Studio version label in:

content/copilot/concepts/billing/usage-based-billing-for-individuals.md

In the "Update your IDE, client, and extension" table, the row currently says:

  • Visual Studio 2025 (18.x)

It should be:

  • Visual Studio 2026 (18.x)

Why

The year label is inconsistent with the intended product version naming and appears to be a typo.

Changes made

  • Updated 2025 to 2026 in the Visual Studio row.

Copilot AI review requested due to automatic review settings June 24, 2026 03:40
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Jun 24, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the minimum supported IDE versions table in the Copilot usage-based billing documentation to correct the Visual Studio release year label, keeping the guidance aligned with Microsoft’s current major-version naming.

Changes:

  • Changed the table row label from “{% data variables.product.prodname_vs %} 2025 (18.x)” to “{% data variables.product.prodname_vs %} 2026 (18.x)”.

@6691tmr

6691tmr commented Jun 25, 2026

Copy link
Copy Markdown

6691tmr added a commit to 1966tmr/docs-6691tmr- that referenced this pull request Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants