Spelling Fixes

[ArieHein]

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.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• 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

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[Copilot]

Pull Request Overview

This PR corrects various spelling mistakes in help messages, comments, and resource strings without changing any program logic.

• Fixed typos in PowerShell cmdlet help messages (e.g., “asssociate” → “associate”, “gatway” → “gateway”).
• Corrected comment spelling errors (e.g., “operaitonId” → “operationId”, “insensistive” → “insensitive”).
• Updated displayable resource strings and XML comments across multiple modules.

Reviewed Changes

Copilot reviewed 32 out of 33 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
UpdateAzureVirtualNetworkGatewayCommand.cs	HelpMessage spelling fixes (“assiociate” → “associate”)
ResizeAzureVirtualNetworkGatewayCommand.cs	HelpMessage spelling fix (“gatway” → “gateway”)
NewAzureVpnClientConnectionConfigurationCommand.cs	HelpMessage spelling fix (“Associatted” → “Associated”)
NewAzureVirtualNetworkGatewayCommand.cs	HelpMessage spelling fixes (“assiociate” → “associate”)
InvokeAzureVirtualNetworkGatewayPrepareMigrationCommand.cs	HelpMessage spelling fix (“paramters” → “parameters”)
GenerateAzureVpnClientPackage.cs	Comment spelling fix (“Poweshell” → “Powershell”)
AzureVirtualNetworkSubnetConfigHelper.cs	Comment spelling fix (“NetworkIdentier” → “NetworkIdentifier”)
Resources.resx	Resource string fix (“configuraiton” → “configuration”)
ProviderConfiguration.cs	XML comment fix (“priavte endopoint” → “private endpoint”)
AzureRMExpressRouteCrossConnectionPeeringBase.cs	Comment fix (“PeerAddresType” → “PeerAddressType”)
AddAzureRMExpressRouteCrossConnectionPeeringCommand.cs	Comment fix (“PeerAddresType” → “PeerAddressType”)
SetAzureExpressRouteCircuitPeeringConfigCommand.cs	Comment fix (“PeerAddresType” → “PeerAddressType”)
NewAzureExpressRouteCircuitPeeringConfigCommand.cs	Comment fix (“PeerAddresType” → “PeerAddressType”)
Remove/Get/Add*AzureExpressRouteCircuitConnectionConfigCommand.cs	HelpMessage typo fix (“intiating” → “initiating”)
AzureExpressRouteCircuitPeeringConfigBase.cs	Comment fix (“PeerAddresType” → “PeerAddressType”)
AddAzureExpressRouteCircuitPeeringConfigCommand.cs	Comment fix (“PeerAddresType” → “PeerAddressType”)
GetAzureRmVirtualWanVpnServerConfigurationVpnProfileCommand.cs	HelpMessage fix (“configuraiton” → “configuration”)
Update/Remove/NewAzureRmVHubRouteTableCommand.cs	Comment fix (“thorw” → “throw”)
New/Set/RemoveAzureRmRoutingIntentCommand.cs	Comment fix (“thorw” → “throw”)
Update/Remove/NewAzureRmRouteMapCommand.cs	Comment fix (“thorw” → “throw”)
NetworkResourceManagerProfile.cs	Comment fixes (“Avaliable” → “Available”, “NetworkSecrityRule” → “NetworkSecurityRule”, “ExoressRouteCircuitAuthorization” → “ExpressRouteCircuitAuthorization”)
NetworkClient.cs	Comment spelling fixes (“operaitonId” → “operationId”)
NewAzureFirewallPolicyNetworkRuleCommand.cs	Comment fix (“exclusitivity” → “exclusivity”)
AzureFirewallFqdnTagHelper.cs	Comment fix (“insensistive” → “insensitive”)

Files not reviewed (1)

• src/Network/Network/Properties/Resources.Designer.cs: Language not supported

[microsoft-github-policy-service]

Thank you for your contribution @ArieHein! We will review the pull request and get back to you soon.

[YanaXu]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).