Spelling Fixes
Description
This does spelling fixes in codebase files that are either:
- in comments.
- in displayable strings.
One change to a ps1 file for testing that is scoped to this file only.
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.)
- [ ] General release
- [ ] Public preview
- [ ] Private preview
- [ ] Engineering build
- [x] No need for a release
-
[x] Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:
-
SHOULD update
ChangeLog.mdfile(s) appropriately- Update
src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.- A snippet outlining the change(s) made in the PR should be written under the
## Upcoming Releaseheader in the past tense.
- A snippet outlining the change(s) made in the PR should be written under the
- Should not change
ChangeLog.mdif no new release is required, such as fixing test case only.
- Update
- SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
- SHOULD have proper test coverage for changes in pull request.
- SHOULD NOT adjust version of module manually in pull request
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.
/azp run azure-powershell - security-tools
Azure Pipelines successfully started running 1 pipeline(s).
@vidai-msft on the same topic of generation, there are some files under the Generated subfolder in each module, if there are spelling fixes there, where is the original source of them ?
@vidai-msft on the same topic of generation, there are some files under the Generated subfolder in each module, if there are spelling fixes there, where is the original source of them ?
@ArieHein The source is the swagger repo. https://github.com/Azure/azure-rest-api-specs
/azp run azure-powershell - security-tools
Azure Pipelines successfully started running 1 pipeline(s).