Merge pull request #11550 from Blake-Madden/main

chrisda · web-flow · commit 71dc6785e4a7 · 2024-01-03T09:59:10.000-08:00
Fix a few typos
diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -274,7 +274,7 @@ All versions of the module are supported in Windows PowerShell 5.1.
 
 PowerShell 7 on Windows requires version 2.0.4 or later.
 
-Version 2.0.5 or later of the module requires the Microsoft .NET Framework 4.7.2 or later to connect. Otherwise, you'll get an `System.Runtime.InteropServices.OSPlatform` error. This requirement shouldn't be an issue in current versions of Windows. For more information about versions of Windows that support the .NET Framework 4.7.2, see [this article](/dotnet/framework/migration-guide/versions-and-dependencies#net-framework-472).
+Version 2.0.5 or later of the module requires the Microsoft .NET Framework 4.7.2 or later to connect. Otherwise, you'll get a `System.Runtime.InteropServices.OSPlatform` error. This requirement shouldn't be an issue in current versions of Windows. For more information about versions of Windows that support the .NET Framework 4.7.2, see [this article](/dotnet/framework/migration-guide/versions-and-dependencies#net-framework-472).
 
 Windows PowerShell requirements and module support **in older versions of Windows** are described in the following list:
 
@@ -370,7 +370,7 @@ To install the module for the first time, complete the following steps:
 
 3. Now you can use the **Install-Module** cmdlet to install the module from the PowerShell Gallery. Typically, you'll want the latest public version of the module, but you can also install a Preview version if any are available.
 
-   - To install **the latest public version** of the module, run **one** of the the following commands:
+   - To install **the latest public version** of the module, run **one** of the following commands:
 
      - In an elevated PowerShell window (all users):
 
diff --git a/exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md
@@ -75,7 +75,7 @@ Type: RuleState
 Parameter Sets: (All)
 Aliases:
 Accepted values: Enabled, Disabled
-Applicable: Exchange Onlinen
+Applicable: Exchange Online
 
 Required: False
 Position: Named
diff --git a/exchange/exchange-ps/exchange/Get-ConnectionInformation.md b/exchange/exchange-ps/exchange/Get-ConnectionInformation.md
@@ -52,9 +52,9 @@ The output of the cmdlet contains the following properties:
 - CertificateAuthentication: Whether certificate based authentication (also known as CBA or app-only authentication) was used to connect. Values are True or False.
 - ModuleName: The filename and path of the temporary data for the session. For example, C:\Users\laura\AppData\Local\Temp\tmpEXO_a54z135k.qgv
 - ModulePrefix: The value specified using the Prefix parameter in the Connect-ExchangeOnline or Connect-IPPSSession command.
-- Organization: The value specified using the the Organization parameter in the Connect-ExchangeOnline or Connect-IPPSSession command for CBA or managed identity connections.
-- DelegatedOrganization: The value specified using the the DelegatedOrganization parameter in the Connect-ExchangeOnline or Connect-IPPSSession command.
-- AppId: The value specified using the the AppId parameter in the Connect-ExchangeOnline or Connect-IPPSSession command for CBA connections.
+- Organization: The value specified using the Organization parameter in the Connect-ExchangeOnline or Connect-IPPSSession command for CBA or managed identity connections.
+- DelegatedOrganization: The value specified using the DelegatedOrganization parameter in the Connect-ExchangeOnline or Connect-IPPSSession command.
+- AppId: The value specified using the AppId parameter in the Connect-ExchangeOnline or Connect-IPPSSession command for CBA connections.
 - PageSize: The default maximum number of entries per page in the connection. The default value is 1000, or you can use the PageSize parameter in the Connect-ExchangeOnline command to specify a lower number. Individual cmdlets might also have a PageSize parameter.
 - TenantID: The tenant ID GUID value. For example, 3750b40b-a68b-4632-9fb3-5b1aff664079.
 - TokenStatus: For example, Active.
diff --git a/exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md b/exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md
@@ -51,7 +51,7 @@ This example returns information about delegate access to IRM-protected messages
 Get-MailboxIRMAccess -Identity lynette@contoso.onmicrosoft.com -User chris@contoso.onmicrosoft.com
 ```
 
-This example returns information about delegate Chris' access access to IRM-protected messages in Lynette's mailbox.
+This example returns information about delegate Chris' access to IRM-protected messages in Lynette's mailbox.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/exchange/New-ComplianceCase.md b/exchange/exchange-ps/exchange/New-ComplianceCase.md
@@ -79,7 +79,7 @@ The CaseType parameter specifies the type of compliance case that you want to cr
 - DataInvestigation: Data investigation cases are used to investigate data spillage incidents.
 - DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations.
 - eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. This is the default value.
-- InsiderRisk: Insider risk cases are use to manage insider risk management cases. Typically, insider risk management cases are manually created in the Microsoft Purview compliance portal to further investigate activity based on an risk alert.
+- InsiderRisk: Insider risk cases are use to manage insider risk management cases. Typically, insider risk management cases are manually created in the Microsoft Purview compliance portal to further investigate activity based on a risk alert.
 - InternalInvestigation: This value is reserved for internal Microsoft use.
 - SupervisionPolicy: This type of case corresponds to communication compliance policy.
 
diff --git a/exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md b/exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 ### -CustomExternalBody
 The CustomExternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks (").
 
-This parameter is meaningful only when the the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true:
+This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true:
 
 - EnableExternalSenderAdminNotifications
 - EnableExternalSenderNotifications
diff --git a/exchange/exchange-ps/exchange/New-ReceiveConnector.md b/exchange/exchange-ps/exchange/New-ReceiveConnector.md
@@ -1148,7 +1148,7 @@ Accept wildcard characters: False
 ### -MaxAcknowledgementDelay
 This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments.
 
-The MaxAcknowledgementDelay parameter specifies the maximum period the transport server delays acknowledgement until it verifies that the message has been successfully delivered to all recipients. When receiving messages from a host that doesn't support shadow redundancy, an Exchange Server 2010 transport server will delay issuing an acknowledgement until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server will time out and issue an acknowledgement anyway.
+The MaxAcknowledgementDelay parameter specifies the maximum period the transport server delays acknowledgment until it verifies that the message has been successfully delivered to all recipients. When receiving messages from a host that doesn't support shadow redundancy, an Exchange Server 2010 transport server will delay issuing an acknowledgment until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server will time out and issue an acknowledgment anyway.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
diff --git a/exchange/exchange-ps/exchange/Remove-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/Remove-UnifiedAuditLogRetentionPolicy.md
@@ -49,7 +49,7 @@ This example deletes the audit log retention policy named "SearchQueryPerformed
 The Identity parameter specifies the audit log retention policy that you want to delete. You can use any value that uniquely identifies the policy. For example:
 
 - Name
-- Distingished name (DN)
+- Distinguished name (DN)
 - GUID
 
 ```yaml
diff --git a/exchange/exchange-ps/exchange/Set-ComplianceSearch.md b/exchange/exchange-ps/exchange/Set-ComplianceSearch.md
@@ -339,7 +339,7 @@ This parameter is available only in the cloud-based service.
 
 The HoldNames parameter specifies that the content locations that have been placed on hold in the eDiscovery case will be searched. You use the value All for this parameter. You can use this parameter only for compliance searches that are associated with an eDiscovery case.
 
-If the content locations in the compliance search include mailboxes, you also need to use the ExchangeLocation parameter with the value $null. Similarly, if the compliance search includes SharePoint sites, you also need to use the SharePointLocation parameter withthe value $null.
+If the content locations in the compliance search include mailboxes, you also need to use the ExchangeLocation parameter with the value $null. Similarly, if the compliance search includes SharePoint sites, you also need to use the SharePointLocation parameter with the value $null.
 
 Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you restart this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search.
 
diff --git a/exchange/exchange-ps/exchange/Set-MalwareFilterPolicy.md b/exchange/exchange-ps/exchange/Set-MalwareFilterPolicy.md
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 ### -CustomExternalBody
 The CustomExternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks (").
 
-This parameter is meaningful only when the the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true:
+This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true:
 
 - EnableExternalSenderAdminNotifications
 - EnableExternalSenderNotifications
diff --git a/exchange/exchange-ps/exchange/Set-ManagementScope.md b/exchange/exchange-ps/exchange/Set-ManagementScope.md
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 ```
 
 ### -RecipientRoot
-The RecipientRoot parameter specifies the organizational unit (OU) under which the filter specified with the RecipientRestrictionFilter parameter should be applied. Valid input for this parameter is an OU or domain that's visibor domain that's returned bylUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
+The RecipientRoot parameter specifies the organizational unit (OU) under which the filter specified with the RecipientRestrictionFilter parameter should be applied. Valid input for this parameter is an OU or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
 - Name
 - Canonical name
diff --git a/exchange/exchange-ps/exchange/Set-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/Set-SafeAttachmentPolicy.md
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 ### -RedirectAddress
 The RedirectAddress parameter specifies the destination email address to deliver messages if malware is detected in an attachment.
 
-The value of this parameter is meaningful only when when value of the Redirect parameter is $true and the value of the Action parameter is Allow.
+The value of this parameter is meaningful only when value of the Redirect parameter is $true and the value of the Action parameter is Allow.
 
 **Note**: Redirection will soon be available only for the Allow action. For more information, see [MC424899](https://admin.microsoft.com/AdminPortal/Home?#/MessageCenter/:/messages/MC424899).
 
diff --git a/exchange/exchange-ps/exchange/Set-UMMailbox.md b/exchange/exchange-ps/exchange/Set-UMMailbox.md
@@ -81,7 +81,7 @@ This example prevents the user tony@contoso.com from accessing his calendar and
 ## PARAMETERS
 
 ### -Identity
-The Identity parameter specifies the mailbox tht you want to modify. You can use any value that uniquely identifies the mailbox. For example:
+The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
 - Name
 - Alias
diff --git a/exchange/exchange-ps/exchange/Set-X400AuthoritativeDomain.md b/exchange/exchange-ps/exchange/Set-X400AuthoritativeDomain.md
@@ -83,7 +83,7 @@ This example makes the following changes to an existing X.400 authoritative doma
 ## PARAMETERS
 
 ### -Identity
-The Identity parameter specifies the X.400 authoritative domain tht you want to modify. You can use any value that uniquely identifies the domain. For example:
+The Identity parameter specifies the X.400 authoritative domain that you want to modify. You can use any value that uniquely identifies the domain. For example:
 
 - Name
 - Distinguished name (DN)
diff --git a/exchange/exchange-ps/exchange/Start-MailboxAssistant.md b/exchange/exchange-ps/exchange/Start-MailboxAssistant.md
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 ```
 
 ### -SoftDeletedMailbox
-The SoftDeletedMailbox switch specifies that the mailbox to be processed by the assistant is a soft-delted mailbox.
+The SoftDeletedMailbox switch specifies that the mailbox to be processed by the assistant is a soft-deleted mailbox.
 
 Soft-deleted mailboxes are deleted mailboxes that are still recoverable.
 
diff --git a/skype/skype-ps/skype/Get-CsOnlineVoiceRoute.md b/skype/skype-ps/skype/Get-CsOnlineVoiceRoute.md
@@ -30,7 +30,7 @@ Get-CsOnlineVoiceRoute [-Filter <string>] [<CommonParameters>]
 ## DESCRIPTION
 Use this cmdlet to retrieve one or more existing online voice routes in your tenant. Online voice routes contain instructions that tell Skype for Business Online how to route calls from Office 365 users to phone numbers on the public switched telephone network (PSTN) or a private branch exchange (PBX).
 
-This cmdlet can be used to retrieve voice route information such as which online PSTN gateways the route is associated with (if any), which online PSTN usages are associated with the route, the pattern (in the form of a regular expression) that identifies the phone numbers to which the route applies, and caller ID settings. The PSTN usage associates the voice route to a online voice policy.
+This cmdlet can be used to retrieve voice route information such as which online PSTN gateways the route is associated with (if any), which online PSTN usages are associated with the route, the pattern (in the form of a regular expression) that identifies the phone numbers to which the route applies, and caller ID settings. The PSTN usage associates the voice route to an online voice policy.
 
 This cmdlet is used when configuring Microsoft Phone System Direct Routing.
 
diff --git a/skype/skype-ps/skype/Grant-CsTeamsCallParkPolicy.md b/skype/skype-ps/skype/Grant-CsTeamsCallParkPolicy.md
@@ -16,7 +16,7 @@ ms.reviewer:
 
 The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams.  Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different Teams phone.  The Grant-CsTeamsCallParkPolicy cmdlet lets you assign a custom policy to a specific user.
 
-NOTE: the call park feature currently only available in desktop, web clients and mobile clients.  Call Park functionality is currently on the roadmap for Teams IP Phones.  Supported with TeamsOnly mode for users with the Phone Sytem license
+NOTE: the call park feature currently only available in desktop, web clients and mobile clients.  Call Park functionality is currently on the roadmap for Teams IP Phones.  Supported with TeamsOnly mode for users with the Phone System license
 
 ## SYNTAX
 
diff --git a/skype/skype-ps/skype/Invoke-CsPoolFailOver.md b/skype/skype-ps/skype/Invoke-CsPoolFailOver.md
@@ -112,7 +112,7 @@ When present, indicates that failover is being performed in "disaster mode." If
 
 If this parameter is not present that means that the pool is still up and running and that failover occurred by administrator choice; for example, the pool might temporarily be failed over in order to do hardware or software upgrades on the server.
 
-Note: The parameteris required for an Enterprise pool if the backend SQL services are down but the front end servers are still up.
+Note: The parameters required for an Enterprise pool if the backend SQL services are down but the front end servers are still up.
 
 
 
diff --git a/skype/skype-ps/skype/Move-CsRgsConfiguration.md b/skype/skype-ps/skype/Move-CsRgsConfiguration.md
@@ -28,7 +28,7 @@ When someone calls a designated phone number, that call can be automatically rou
 Alternatively, the call might be routed to an interactive voice response (IVR) queue.
 In that queue, the caller would be asked a series of questions (for example, "Are you calling about an existing order?") and then, based on the answers to those questions, be given the asked-for information or be routed to a Response Group agent.
 
-If you are currently running the Response Group application on legacy server, the Move-CsRgsConfiguration cmdlet provides a way for you to migrate this service to newer vesion server.
+If you are currently running the Response Group application on legacy server, the Move-CsRgsConfiguration cmdlet provides a way for you to migrate this service to newer version server.
 To migrate the service, you need to call the Move-CsRgsConfiguration cmdlet and specify: 1) the fully qualified domain name (FQDN) for the existing version of the Response Group application (the Source); and, 2) the FQDN for the new Skype for Business Server version of the service (the Destination).
 Move-CsRgsConfiguration will then move all the configuration settings, audio files, and contact objects from the existing version (for example, Office Communications Server 2007 R2 or Lync Server 2010) to newer version.
 After the service has been migrated, all calls to a Response Group phone number will be handled by the newer server.
diff --git a/skype/skype-ps/skype/Move-CsUser.md b/skype/skype-ps/skype/Move-CsUser.md
diff --git a/skype/skype-ps/skype/New-CsClientPolicy.md b/skype/skype-ps/skype/New-CsClientPolicy.md
diff --git a/skype/skype-ps/skype/Remove-CsOnlineSchedule.md b/skype/skype-ps/skype/Remove-CsOnlineSchedule.md
diff --git a/skype/skype-ps/skype/Set-CsOnlineDialInConferencingBridge.md b/skype/skype-ps/skype/Set-CsOnlineDialInConferencingBridge.md
diff --git a/teams/teams-ps/teams/Get-CsPhoneNumberAssignment.md b/teams/teams-ps/teams/Get-CsPhoneNumberAssignment.md
diff --git a/teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md b/teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md
diff --git a/teams/teams-ps/teams/Remove-CsPhoneNumberAssignment.md b/teams/teams-ps/teams/Remove-CsPhoneNumberAssignment.md
diff --git a/teams/teams-ps/teams/Remove-TeamChannelUser.md b/teams/teams-ps/teams/Remove-TeamChannelUser.md
