Spelling Fixes (#27953)

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Vincent Dai <23257217+vidai-msft@users.noreply.github.com>

Author: 3 people

documentation/breaking-changes/breaking-changes-in-generated-modules-due-to-codegen-tool-upgrade-from-v3-to-v4.md

@@ -27,7 +27,7 @@ Generally, this change will not cause a breaking change for users. In modules ge
 
 ### Removal of PassThru for Certain Cmdlets
 
-`-PassThru` is a switch parameter that we add to cmdlets that don't have outputs to enable the pipline functionality. In AutoRest.PowerShell v3, `-PassThru` was incorrectly added to some cmdlets that do have outputs. This is fixed in v4 and those extra `-PassThru` parameters are removed.
+`-PassThru` is a switch parameter that we add to cmdlets that don't have outputs to enable the pipeline functionality. In AutoRest.PowerShell v3, `-PassThru` was incorrectly added to some cmdlets that do have outputs. This is fixed in v4 and those extra `-PassThru` parameters are removed.
 
 #### How to Mitigate the Impact of Breaking Changes
 

documentation/development-docs/azure-powershell-developer-guide.md

@@ -233,7 +233,7 @@ To import modules automatically when debug has started, follow the below steps:
 - Please refer to [Debug Page, Project Designer](https://learn.microsoft.com/visualstudio/ide/reference/debug-page-project-designer?view=vs-2022) for how to access the Debug page
 - Create a **Excutable** new Debug profile
 - For Azure PowerShell, please setup debug profile in the following way
-  - Set **Excutable** to the path of the excutable file of PowerShell core, for example,`C:\Program Files\PowerShell\7\pwsh.exe`
+  - Set **Excutable** to the path of the executable file of PowerShell core, for example,`C:\Program Files\PowerShell\7\pwsh.exe`
   - Import the Profile module, along with the module you are testing, by pasting the following in the **Command line arguments** box (_note_: you have to update the <PATH_TO_REPO> and <SERVICE> values provided below):
     - `-NoExit -Command "Import-Module <PATH_TO_REPO>/artifacts/Debug/Az.Accounts/Az.Accounts.psd1;Import-Module <PATH_TO_REPO>/artifacts/Debug/Az.<SERVICE>/Az.<SERVICE>.psd1;$DebugPreference='Continue'"`
 

documentation/development-docs/breakingchange-for-autogen-module.md

@@ -116,9 +116,9 @@ Breaking changes and preview messages for auto gen cmdlets are added through dir
 
 To add breaking changes or preview messages for a customized cmdlets, you will need to add related attributes in code directly. And following are some common cases.
 
-You must provide expected breaking change az version and moudle verision otherwise it won't compile. The first version is expected az version while the second one is expected moudle verision.
+You must provide expected breaking change az version and module version otherwise it won't compile. The first version is expected az version while the second one is expected module version.
 
-**Note: these examples are based on the Az.Databricks module. Please double check the namesapce. You will most likely need to replace "Databricks" with your module's name.**
+**Note: these examples are based on the Az.Databricks module. Please double check the namespace. You will most likely need to replace "Databricks" with your module's name.**
 
 ## Case 1 — Generic Breaking change for a cmdlet
 

documentation/development-docs/design-guidelines/azure-powershell-exceptions.md

@@ -17,7 +17,7 @@ Azure PowerShell defines most commonly used exceptions, all of which inherit fro
 | AzPSInvalidOperationException | Internal |  | This exception should be thrown when a method call is invalid for the object's current state. |
 | AzPSIOException | User |  | This exception should be thrown when an I/O error occurs. |
 | AzPSKeyNotFoundException | Internal | MapKeyName | This exception should be thrown when the key specified for accessing an element in a collection does not match any key in the collection. |
-| AzPSApplicationException | Internal |  | This exception is representive of ApplicationException in Azure PowerShell. |
+| AzPSApplicationException | Internal |  | This exception is representative of ApplicationException in Azure PowerShell. |
 | AzPSFileNotFoundException | User | FileName (Not full path) | This exception should be thrown when accessing a file that does not exist. |
 
 There are three types of errors in Azure PowerShell.

documentation/development-docs/design-guidelines/managed-identity-best-practices.md

@@ -64,7 +64,7 @@ If the module is under pre-GA status, we can let the syntax break directly due t
 If the module is GAed, we need to disable the transform (See guideline at [here](https://github.com/Azure/autorest.powershell/blob/main/docs/migration-from-v3-to-v4.md#how-to-mitigate-the-breaking-changes-of-managed-identity-best-practice-alignment).) but preannounce breaking change)  and plan to break it (add upcoming breaking changes for them and take the effects on a major release).
 
 ### What should I do if Autorest reports _"Parameter IdentityType in operation '{operationId}' can not be transformed as the best practice design"_?
-This error indicates that autorest is trying to replace PATCH operation by GET+PUT operation to let IdentityType transformed as best practice desgin but failed due to certain reasons. One of common reasons is GET operation contains query parameter and autorest has not supported such a combined GET+PUT operation. To mitigate this issue, 
+This error indicates that autorest is trying to replace PATCH operation by GET+PUT operation to let IdentityType transformed as best practice design but failed due to certain reasons. One of common reasons is GET operation contains query parameter and autorest has not supported such a combined GET+PUT operation. To mitigate this issue, 
 
 - Include a customization script to transform the parameter IdentityType to EnableSystemAssignedIdentity by `get` + `patch` update for this type of operation. The following are the detailed steps on how to accomplish this.
   - disable transformation for the operation which reported error in README.md by

documentation/development-docs/generate-format.ps1xml-file.md

@@ -83,7 +83,7 @@ namespace Microsoft.Azure.Commands.Profile.Models
 // code omitted for brevity 
 ```
 
-PowerShell uses these properties for the cmdlet table formated output:
+PowerShell uses these properties for the cmdlet table formatted output:
 
 ```PowerShell
 PS C:\> Get-AzSubscription | Format-Table

documentation/development-docs/sdkbased-vs-autogen.md

@@ -1,6 +1,6 @@
 # Description
 
-The document is for those, who are familiar with SDK-based modules and want to give a try with auto-gen modules. The content will contain the comparation between these two kinds of modules from architecture, cmdlets differences, and onboard process, etc.
+The document is for those, who are familiar with SDK-based modules and want to give a try with auto-gen modules. The content will contain the comparison between these two kinds of modules from architecture, cmdlets differences, and onboard process, etc.
 
 # Architecture
 
@@ -65,7 +65,7 @@ Customization could be done through three ways.
 
 ### SDK-based Module
 
-If your module relies on some other modules, you will need to rely on dotnet SDK of these modules, which could put in your module if only your module depends on them or in Az.Accouts they are some common modules required by several modules. 
+If your module relies on some other modules, you will need to rely on dotnet SDK of these modules, which could put in your module if only your module depends on them or in Az.Accounts they are some common modules required by several modules. 
 
 ### Auto-gen Module
 

documentation/internal/authinrdfe.md

@@ -13,15 +13,15 @@ To acquire management certificate credentials, you must download  a PublishingPr
 The Add-AzureAccount command can be used to acquire a token based on user credentials, and if the associated user is authorized for RDFE access to a subscription (they must be a classic administrator or co-admin of the subscription), they will have access to those subscriptions authorized to their account for classic administrator access
 
 ## General Notes
-- Managemnt certificate authentication lasts for an entire TCP session.  User authentication is self-renewing, just as it is in ARM.
+- Management certificate authentication lasts for an entire TCP session.  User authentication is self-renewing, just as it is in ARM.
 
 ## Programmatic Authentication for PowerShell clients
 - Clients are still authenticated using an IAuthenticationFactory, and the following overload:
 
 ```c#
 SubscriptionCloudCredentials GetSubscriptionCloudCredentials(IAzureContext context)
 ```
-Note that, the ARM token audience is different than the token audience used for RDFE, although the RDFE tolken audience is accepted by both endpoints.
+Note that, the ARM token audience is different than the token audience used for RDFE, although the RDFE token audience is accepted by both endpoints.
 
 Similarly, RDFE clients can be created using the IClientFactory interface: 
 

documentation/internal/pull-request-review-knowledge-share.md

@@ -1,11 +1,11 @@
 ## PR Review Knowledge Share
 
-### Dependency Assemlby Version Confliction
+### Dependency Assembly Version Confliction
 If one assembly has been referenced by more than one module, we should let Az.Accounts to handle the dependency.
 
 **RED** flag
 - Update assembly version for common Microsoft.Extensions.*
-- Add new dependency assemlby for one module, the assembly may be referenced by other module already.
+- Add new dependency assembly for one module, the assembly may be referenced by other module already.
 - Contains version update for dependency assembly in module other than Az.Accounts
 
 ### Resource ID **MUST** start with a slash 

documentation/migration-guides/Az.11.0.0-migration-guide.md

@@ -682,8 +682,8 @@ The cmdlet 'Reset-AzPowerBIWorkspaceCollectionAccessKey' has been removed as Wor
 
 ## AZ.Storage
 
-### `Get-AzStorageQueueStoredAcessPolicy`
-Permissions in the ouput access policy is changed to a string like "raup"
+### `Get-AzStorageQueueStoredAccessPolicy`
+Permissions in the output access policy is changed to a string like "raup"
 
 ### `New-AzStorageAccountSasToken`
 The leading question mark '?' of the created SAS token is removed
@@ -707,5 +707,5 @@ The leading question mark '?' of the created SAS token is removed
 The leading question mark '?' of the created SAS token is removed
 
 ### `Set-AzStorageQueueStoredAccessPolicy`
-Permissions in the ouput access policy is changed to a string like "raup"
+Permissions in the output access policy is changed to a string like "raup"