-
Notifications
You must be signed in to change notification settings - Fork 4k
Spelling Fixes #28093
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
Spelling Fixes #28093
Conversation
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this 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 PR corrects spelling mistakes in comments, display strings, and documentation across the codebase without altering behavior.
- Fixed typos in PowerShell test scripts and Markdown examples
- Corrected resource strings and XML comments in C# files
- Updated help messages, error text, and summary comments
Reviewed Changes
Copilot reviewed 26 out of 27 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
src/StreamAnalytics/.../utils.ps1 | Fixed “learing” → “learning” |
src/StreamAnalytics/.../Remove-AzStreamAnalyticsCluster.md | Fixed “brefore” → “before” |
src/StreamAnalytics/.../README.md | Fixed “staus” → “status”, “deleteing” → “deleting” |
src/StorageSync/.../StorageSyncResources.resx | Fixed “Succesfully” → “Successfully” |
src/StorageSync/.../ProgressReporter.cs | Fixed XML comment grammar |
src/StorageSync/.../NamespaceEnumerator.cs | Fixed “operaiton” → “operation” and “emited” → “emitted” |
src/StorageSync/.../ServerManagedIdentityUtils.cs | Fixed “chellenge” → “challenge” |
src/StorageSync/.../ServerManagedIdentityTokenHelper.cs | Fixed “asociated” → “associated” |
src/StorageSync/.../Win32Helper.cs | Fixed “Coes” → “Does”, “capababilities” → “capabilities” |
src/StorageSync/.../SyncServerRegistrationClient.cs | Fixed “Parameterzed” → “Parameterized”, “clooud” → “cloud” |
src/StorageSync/.../SyncServerCertificateRolloverClient.cs | Fixed “Parameterzed” → “Parameterized” |
src/StorageSync/.../EcsManagementInteropClient.cs | Fixed “stbale” → “stable”, “Coes” → “Does”, “capababilities” → “capabilities” |
src/StorageSync/.../ServerRoleType.cs | Fixed “Stadalone” → “Standalone” |
src/StorageSync/.../IStorageSyncResourceManager.cs | Fixed “propogation” → “propagation” |
src/StorageSync/.../IPowershellCommandRunner.cs | Fixed “Errorses” → “Errors” |
src/StorageSync/.../INamespaceEnumeratorListener.cs | Fixed “Nexts” → “Next” |
src/StorageSync/.../Configuration.cs | Fixed “Includeses” → “Includes”, “Executings” → “Executing” |
src/StorageSync/.../StorageSyncResourceManager.cs | Fixed “propogation” → “propagation” |
src/StorageSync/.../HelpMessages.cs | Fixed parameter description typo |
src/StorageSync/.../InvokeCompatibilityCheckCmdlet.cs | Fixed “creentials” → “credentials” |
src/StorageSync/.../AFSDirectoryInfo.cs | Fixed “Existses” → “Exists” |
src/StorageSync.Test/.../MockFactory.cs | Fixed “Directorieses” → “Directories” |
src/StorageSync.Test/.../MaximumPathLengthValidationTest.cs | Fixed “parth” → “path” |
src/StorageSync.Test/.../MockSyncServerRegistrationClient.cs | Fixed “clooud” → “cloud”, “gurantee” → “guarantee” |
src/StorageSync.Test/.../MockStorageSyncResourceManager.cs | Fixed “propogation” → “propagation” |
Files not reviewed (1)
- src/StorageSync/StorageSync/Properties/StorageSyncResources.Designer.cs: Language not supported
Thank you for your contribution @ArieHein! We will review the pull request and get back to you soon. |
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
This does spelling fixes in codebase files that are either:
in comments.
in displayable strings.
There are NO other changes to programmatic aspects or code behavior.
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.