-
Notifications
You must be signed in to change notification settings - Fork 4k
Spelling Fixes #27923
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 #27923
Conversation
adding additional findings Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
Thank you for your contribution @ArieHein! We will review the pull request and get back to you soon. |
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 fixes various spelling mistakes in the Network module’s PowerShell help files.
- Corrected “commandlet” to “cmdlet” and other cmdlet spelling variants.
- Fixed typos like “configuraiton”, “subscritption”, “rollection”, and similar.
- Updated sample descriptions to correct misspellings.
Reviewed Changes
Copilot reviewed 54 out of 54 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
Get-AzVpnClientConfiguration.md | Fixed “commandlet” → “cmdlet” |
Get-AzVirtualWanVpnServerConfigurationVpnProfile.md | Corrected “configuraiton” → “configuration” |
Get-AzVirtualWanVpnServerConfiguration.md | Fixed “VirutalHubs” → “VirtualHubs” |
Get-AzVirtualWanVpnConfiguration.md | Changed “commandlet” → “cmdlet” in two sentences |
Get-AzVirtualNetworkGatewaySupportedVpnDevice.md | Updated “commandlet” → “cmdlet” in synopsis and description |
Get-AzVirtualNetworkGatewayConnectionVpnDeviceConfigScript.md | Changed “commandlet” → “cmdlet” in synopsis and description |
Get-AzRoutingPolicy.md | Corrected “rouing” → “routing” |
Get-AzPrivateLinkService.md | Changed “commandlet” → “cmdlet” |
Get-AzP2sVpnGatewayConnectionHealth.md | Fixed “aggregared” → “aggregated” |
Get-AzNetworkSecurityPerimeterLoggingConfiguration.md | Fixed “NetworkSsecurityPerimeter” → “NetworkSecurityPerimeter” in examples |
Get-AzNetworkManagerSecurityUserRule.md | Corrected “rollection” → “collection” |
Get-AzNetworkManagerSecurityAdminRule.md | Corrected “rollection” → “collection” |
Get-AzNetworkManagerRoutingRule.md | Corrected “rollection” → “collection” |
Get-AzExpressRouteCircuitMicrosoftPeeringPrefixConfig.md | Fixed “adverised” → “advertised” |
Get-AzBastion.md | Corrected “subscritption” → “subscription” |
Get-AzApplicationGatewayWafDynamicManifest.md | Fixed “athe” → “the” |
Deploy-AzNetworkManagerCommit.md | Corrected “connecitivity” → “connectivity” and “confgurations” → “configurations” |
Az.Network.md | Multiple cmdlet synopsis spelling fixes and “Get-Bastion” text uniformity |
Add-AzRoutingPolicy.md | Corrected “rouing” → “routing” |
Add-AzLoadBalancerRuleConfig.md | Fixed “thrid” → “third” |
Comments suppressed due to low confidence (3)
src/Network/Network/help/Get-AzBastion.md:40
- The bold cmdlet name should match the actual cmdlet; change Get-Bastion to Get-AzBastion for consistency.
The **Get-Bastion** cmdlet gets one or more bastions in a resource group or subscription.
src/Network/Network/help/Add-AzLoadBalancerRuleConfig.md:64
- Typo: use "fourth" instead of "forth".
The forth command will add a new rule with configured backend pools
src/Network/Network/help/Add-AzLoadBalancerRuleConfig.md:65
- Sentence should start with a capital letter: change "the fifth" to "The fifth".
the fifth command will update the load balancer in azure with the new Load Balancer Rule Config.
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
Additional spelling fixes.
Sorry for the amount, but its all in the same topic and covers all cmdlets.
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.