[No QA] Update VAT-IT.md

[stephanieelliott]

Followup to #90391 - removing remaining instances of old name Global VA Tax

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f9bccc61ca

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a targeted terminology correction in VAT-IT.md, replacing two instances of the outdated name "Global VaTax" with the correct product name "VAT IT." This is a straightforward and accurate fix that aligns the article body with its title, metadata, and the rest of the document where "VAT IT" is already used correctly.

Scores Summary

• Readability: 9/10 - The changed lines are clear, concise, and fit naturally into the surrounding content. No issues with sentence flow or scannability.
• AI Readiness: 8/10 - The correction improves retrieval accuracy by ensuring consistent use of the product name "VAT IT" throughout the article, which aligns with the YAML metadata keywords. (Note: The file has pre-existing structural issues outside the scope of this diff — e.g., multiple # headings beyond the title and # FAQ exemption, and the absence of an internalScope field in the frontmatter — but these are not introduced by this PR.)
• Style Compliance: 10/10 - The change correctly applies the exact product name. No naming convention violations are introduced.

Key Findings

• The terminology fix is correct and necessary. The article title, YAML metadata, and most of the body already reference "VAT IT," so these two remaining "Global VaTax" instances were inconsistencies that this PR resolves.
• One pre-existing instance of "Global VaTax" on line 55 (in the "Tracking Your VAT Reclaim" section) appears to have been missed by this PR. Consider updating that occurrence as well for full consistency.

Recommendations

1. Update the remaining instance: Line 55 still reads "...the Submission Analysis Report in Global VaTax." This should likely be changed to "VAT IT" to complete the rename across the entire article.
2. No blockers: The changes as proposed are correct and can be merged. The missed instance on line 55 could be addressed in this PR or a follow-up.

Files Reviewed

• docs/articles/expensify-classic/connections/VAT-IT.md — Two instances of "Global VaTax" correctly updated to "VAT IT." One additional instance on line 55 remains unchanged.

This review assessed only the proposed changes in the diff, not pre-existing content.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://ca16cb18.helpdot.pages.dev ⚡️

Updated articles:

• articles/expensify-classic/connections/VAT-IT

[melvin-bot]

Concierge reviewer checklist:

• I have verified the accuracy of the article
  • The article is within a hub that makes sense, and the navigation is correct
  • All processes, screenshots, and examples align with current product behavior.
  • All links within the doc have been verified for correct destination and functionality.
• I have verified the readability of the article
  • The article's language is clear, concise, and free of jargon.
  • The grammar, spelling, and punctuation are correct.
  • The article contains at least one image, or that an image is not necessary
• I have verified the formatting of the article
  • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
  • The article has proper text spacing and breaks for readability.
• I have verified the article has the appropriate tone and style
  • The article's tone is professional, friendly, and suitable for the target audience.
  • The article's tone, terminology, and voice are consistent throughout.
• I have verified the overall quality of the article
  • The article is not missing any information, nor does it contain redundant information.
  • The article fully addresses user needs.
• I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @VictoriaExpensify

[melvin-bot]

@VictoriaExpensify Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

@VictoriaExpensify looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[OSBotify]

🚀 Deployed to staging by https://github.com/VictoriaExpensify in version: 9.4.6-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.6-4 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅