Spelling Fixes

[ArieHein]

Description

Additional spelling fixes.

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.

[microsoft-github-policy-service]

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

[Copilot]

Pull Request Overview

This PR corrects various spelling errors in the Azure Synapse PowerShell module help files.

• Fixed misspelled words (e.g., “specififed” → “specified”, “modifys” → “modifies”).
• Aligned terminology consistently (e.g., “firerwall” → “firewall”, “mananged” → “managed”).
• Corrected example typos (e.g., path and identifier names).

Reviewed Changes

Copilot reviewed 27 out of 27 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
Update-AzSynapseWorkspace.md	Fixed “specififed” → “specified” in multiple examples
Update-AzSynapseSparkPool.md	Corrected “tranformed” → “transformed”
Update-AzSynapseFirewallRule.md	Fixed “modifys” → “modifies”; “firerwall” → “firewall”
Restore-AzSynapseSqlPool.md	Fixed “Synaspe” → “Synapse”
Remove-AzSynapseTriggerSubscription.md	Fixed “defintion” → “definition”
Remove-AzSynapseManagedPrivateEndpoint.md	Fixed variable name typo $privateendpint → $privateendpoint
Remove-AzSynapseLinkConnection.md	Fixed “stpped” → “stopped”
Remove-AzSynapseFirewallRule.md	Fixed “firerwall” → “firewall”
New-AzSynapseWorkspacePackage.md	Fixed “pacakge” → “package”
New-AzSynapseFirewallRule.md	Fixed “firerwall” → “firewall”
Invoke-AzSynapseTriggerRun.md	Fixed “InvokByInputObject” → “InvokeByInputObject”
Get-AzSynapseTriggerSubscriptionStatus.md	Fixed “subscribtion” → “subscription”
Get-AzSynapseManagedPrivateEndpoint.md	Fixed “mananged” → “managed”
Get-AzSynapseFirewallRule.md	Fixed “firerwall” → “firewall”
Get-AzSynapseDroppedSqlPool.md	Fixed “Synaspe” → “Synapse”
Export-AzSynapseNotebook.md	Fixed “notbooks” → “notebooks”
Export-AzSynapseKqlScript.md	Fixed “KqlScirpt” → “KqlScript”
Az.Synapse.md	Synced notebook and managed endpoint summaries
Add-AzSynapseTriggerSubscription.md	Fixed “defintion” → “definition”
Add-AzSynapseDataFlowDebugSessionPackage.md	Fixed “Pakcage” → “Package”

Comments suppressed due to low confidence (1)

src/Synapse/Synapse/help/New-AzSynapseWorkspacePackage.md:53

• Typo corrections: change "addes" to "adds" and fix pool name "ContotoSparkPool" to "ContosoSparkPool".

This first command uploads the workspace package whose location is ".\ContosoPackage.whl" to an Azure Synapse workspace named ContosoWorkspace. The workspace package can be either wheel or jar files. Then the second command addes the package to a given Apache Spark pool named ContotoSparkPool.

[vidai-msft]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).