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 addresses various spelling corrections across help documentation for multiple Azure PowerShell modules, improving clarity and consistency.

• Fixed typos in parameter descriptions and examples (e.g., “localtion” → “location”, “assiciated” → “associated”)
• Corrected cmdlet names, boolean literals, and duplicated words in help content

Reviewed Changes

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

Show a summary per file

File	Description
src/DataProtection/DataProtection/help/Initialize-AzDataProtectionRestoreRequest.md	Corrected “localtion” to “location”
src/DataProtection/DataProtection/help/Initialize-AzDataProtectionBackupInstance.md	Fixed “assiciated” → “associated” and “Sanpshot” → “Snapshot”
src/DataProtection/DataProtection/help/Get-AzDataProtectionBackupVault.md	Updated “specity properites” → “specified properties”
src/DataProtection/DataProtection/help/Find-AzDataProtectionRestorableTimeRange.md	Changed “Dispaly” → “Display” and “dicrete” → “discrete”
src/DataProtection/DataProtection/help/Edit-AzDataProtectionPolicyTagClientObject.md	Fixed “Weeky” → “Weekly”
src/DataMigration/DataMigration/help/Remove-AzDataMigrationSqlServiceNode.md	Corrected “Intergration” → “Integration”
src/DataMigration/DataMigration/help/New-AzDataMigrationToSqlDb.md	Fixed “databse” → “database” and “selcted” → “selected”
src/DataMigration/DataMigration/help/Get-AzDataMigrationToSqlVM.md	Fixed resource group name typo (“MyResouceGroup”)
src/DataMigration/DataMigration/help/Az.DataMigration.md	Corrected “databse” → “database”
src/DataFactory/DataFactory/help/Remove-AzDataFactoryV2TriggerSubscription.md	Updated “defintion” → “definition”
src/DataFactory/DataFactory/help/Get-AzDataFactoryV2TriggerSubscriptionStatus.md	Fixed “subscribtion” → “subscription”
src/DataFactory/DataFactory/help/Add-AzDataFactoryV2TriggerSubscription.md	Updated “defintion” → “definition”
src/DataFactory/DataFactory/help/Add-AzDataFactoryV2DataFlowDebugSessionPackage.md	Corrected “Pakcage” → “Package”
src/DataBoxEdge/DataBoxEdge/help/Set-AzDataBoxEdgeBandwidthSchedule.md	Changed “$ture” → “$true”
src/DataBoxEdge/DataBoxEdge/help/New-AzDataBoxEdgeBandwidthSchedule.md	Changed “$ture” → “$true”
src/DataBoxEdge/DataBoxEdge/help/Get-AzDataBoxEdgeTrigger.md	Corrected cmdlet name from “Triger” → “Trigger”
src/DataBox/DataBox/help/Update-AzDataBoxJob.md	Fixed “sytem” → “system”
src/DataBox/DataBox/help/New-AzDataBoxJob.md	Corrected “Disky” → “Disk”
src/CustomProviders/CustomProviders/help/Update-AzCustomProviderAssociation.md	Fixed “provioder” → “provider”
src/CustomProviders/CustomProviders/help/New-AzCustomProviderAssociation.md	Fixed “provioder” → “provider”

Comments suppressed due to low confidence (1)

src/DataBoxEdge/DataBoxEdge/help/Get-AzDataBoxEdgeTrigger.md:40

• [nitpick] Remove the duplicated word 'specific' and consider normalizing 'Triggers' to lowercase for consistency, e.g., 'fetch the details of specific triggers.'

The **Get-AzDataBoxEdgeTrigger** cmdlet gets the triggers for a device. You can specify the name as a parameter in the cmdlet to fetch the details of a specific  specific Triggers

[vidai-msft]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).