Skip to content

Fix typo #126054

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 30, 2025
Merged

Fix typo #126054

merged 1 commit into from
Apr 30, 2025

Conversation

changeworld
Copy link
Contributor

Description

This PR corrects a redundancy in the terminology. The phrase "JWT token" was redundant since "JWT" already stands for "JSON Web Token."

Changes

Replaced "JWT token" with "JWT".

Why this change?

  • Clarity: Avoids redundancy and keeps the terminology precise.
  • Consistency: Aligns with standard usage in technical documentation.

No functional changes.

This is a documentation improvement and does not affect any functionality.

JWT token -> JWT
Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit c17d228:

✅ Validation status: passed

File Status Preview URL Details
articles/synapse-analytics/troubleshoot/troubleshoot-synapse-studio.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@JeneZhang

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 Mar 4, 2025
@v-dirichards v-dirichards merged commit e8db634 into MicrosoftDocs:main Apr 30, 2025
2 checks passed
@changeworld changeworld deleted the patch-159 branch May 1, 2025 00:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment