Skip to content

Conversation

@bgribaudo
Copy link
Contributor

@prmerger-automator
Copy link
Contributor

@bgribaudo : 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 4ea8129:

✅ Validation status: passed

File Status Preview URL Details
query-languages/m/custom-date-and-time-format-strings.md ✅Succeeded

For more details, please refer to the build report.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This pull request continues the terminology standardization effort from PR #385, replacing instances of "throws" with "raises" to align with correct Power Query/M language terminology. In Power Query, errors are "raised" rather than "thrown" (as they would be in languages with exception handling).

Changes:

  • Updated six occurrences of "throws an expression error" to "raises an error" throughout the documentation
  • Updated the ms.date metadata field

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Court72
Copy link
Contributor

Court72 commented Jan 30, 2026

@whhender

Can you review the proposed changes?

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 Jan 30, 2026
Co-authored-by: Ehren <29806264+ehrenMSFT@users.noreply.github.com>
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit f5a0df6:

✅ Validation status: passed

File Status Preview URL Details
query-languages/m/custom-date-and-time-format-strings.md ✅Succeeded

For more details, please refer to the build report.

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.

4 participants