typo: Double word "the"

Author: nschonni

exchange/docs-conceptual/exchange-server/exchange-management-shell.md

@@ -13,7 +13,7 @@ description: "Learn about Exchange Server PowerShell, also known as the Exchange
 ---
 
 # Exchange Server PowerShell (Exchange Management Shell)
-The Exchange Management Shell is built on Windows PowerShell technology and provides a powerful command-line interface that enables the automation of Exchange administration tasks. You can use the Exchange Management Shell to manage every aspect of Exchange. For example, you can create email accounts, create Send connectors and Receive connectors, configure mailbox database properties, and manage distribution groups. You can use the Exchange Management Shell to perform every task that's available in the Exchange graphical management tools, plus things that you can't do there (for example, bulk operations). In fact, when you do something in the the Exchange admin center (EAC), the Exchange Control Panel (ECP), or the Exchange Management Console (EMC), it's the Exchange Management Shell that does the work behind the scenes.
+The Exchange Management Shell is built on Windows PowerShell technology and provides a powerful command-line interface that enables the automation of Exchange administration tasks. You can use the Exchange Management Shell to manage every aspect of Exchange. For example, you can create email accounts, create Send connectors and Receive connectors, configure mailbox database properties, and manage distribution groups. You can use the Exchange Management Shell to perform every task that's available in the Exchange graphical management tools, plus things that you can't do there (for example, bulk operations). In fact, when you do something in the Exchange admin center (EAC), the Exchange Control Panel (ECP), or the Exchange Management Console (EMC), it's the Exchange Management Shell that does the work behind the scenes.
 
 The Exchange Management Shell also provides a robust and flexible scripting platform. Visual Basic scripts that required many lines of code can be replaced by Exchange Management Shell commands that use as little as one line of code. The Exchange Management Shell provides this flexibility because it uses an object model that's based on the Microsoft .NET Framework. This object model enables Exchange cmdlets to apply the output from one command to subsequent commands.
 

exchange/exchange-ps/exchange/client-access/Set-ImapSettings.md

@@ -78,7 +78,7 @@ Set-ImapSettings -X509CertificateName mail.contoso.com
 
 This example specifies the certificate that contains mail.contoso.com is used to encrypt IMAP4 client connections.
 
-**Note**: For single subject certificates or a SAN certificates, you also need to assign the the certificate to the Exchange IMAP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange IMAP service (you'll receive an error if you try).
+**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange IMAP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange IMAP service (you'll receive an error if you try).
 
 ## PARAMETERS
 

exchange/exchange-ps/exchange/client-access/Set-PopSettings.md

@@ -76,7 +76,7 @@ Set-PopSettings -X509CertificateName mail.contoso.com
 
 This example specifies the certificate that contains mail.contoso.com is used to encrypt POP3 client connections.
 
-**Note**: For single subject certificates or a SAN certificates, you also need to assign the the certificate to the Exchange POP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange POP service (you'll receive an error if you try).
+**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange POP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange POP service (you'll receive an error if you try).
 
 ## PARAMETERS
 

exchange/exchange-ps/exchange/database-availability-groups/Test-ReplicationHealth.md

@@ -150,7 +150,7 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-The Identity parameter specifies the the Mailbox server that you want to test.
+The Identity parameter specifies the Mailbox server that you want to test.
 
 You can use any value that uniquely identifies the server. For example:
 

exchange/exchange-ps/exchange/sharing-and-collaboration/New-SiteMailboxProvisioningPolicy.md

@@ -122,7 +122,7 @@ This parameter is available only in on-premises Exchange.
 
 The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are:
 
-- $true: Aliases get the default prefix text. This is the default value. In Office 365, the default prefix text is SMO- (for example, the alias value BugBash\_2016 becomes SMO-BugBash\_2016). In on-premises Exchange, the the default prefix text is SM- (for example, the alias value BugBash\_2016 becomes SM-BugBash\_2016).
+- $true: Aliases get the default prefix text. This is the default value. In Office 365, the default prefix text is SMO- (for example, the alias value BugBash\_2016 becomes SMO-BugBash\_2016). In on-premises Exchange, the default prefix text is SM- (for example, the alias value BugBash\_2016 becomes SM-BugBash\_2016).
 
 - $false: Aliases don't get the default prefix text.
 

exchange/exchange-ps/exchange/sharing-and-collaboration/Set-SiteMailboxProvisioningPolicy.md

@@ -116,7 +116,7 @@ Accept wildcard characters: False
 ### -DefaultAliasPrefixEnabled
 The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are:
 
-- $true: Aliases get the default prefix text. This is the default value. In Office 365, the default prefix text is SMO- (for example, the alias value BugBash\_2016 becomes SMO-BugBash\_2016). In on-premises Exchange, the the default prefix text is SM- (for example, the alias value BugBash\_2016 becomes SM-BugBash\_2016).
+- $true: Aliases get the default prefix text. This is the default value. In Office 365, the default prefix text is SMO- (for example, the alias value BugBash\_2016 becomes SMO-BugBash\_2016). In on-premises Exchange, the default prefix text is SM- (for example, the alias value BugBash\_2016 becomes SM-BugBash\_2016).
 
 - $false: Aliases don't get the default prefix text.
 

sharepoint/sharepoint-ps/sharepoint-server/Get-SPAppStateUpdateInterval.md

@@ -18,7 +18,7 @@ Get-SPAppStateUpdateInterval [-AssignmentCollection <SPAssignmentCollection>] [<
 ```
 
 ## DESCRIPTION
-Use the Get-SPAppStateUpdateInterval cmdlet to return the interval in hours between updates of the the app state update job.
+Use the Get-SPAppStateUpdateInterval cmdlet to return the interval in hours between updates of the app state update job.
 The app state update job updates the app states, including app updates, in SharePoint based on information in the SharePoint Store.
 
 For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at http://go.microsoft.com/fwlink/p/?LinkId=251831 (http://go.microsoft.com/fwlink/p/?LinkId=251831).

sharepoint/sharepoint-ps/sharepoint-server/Set-SPInternalAppStateUpdateInterval.md

@@ -19,7 +19,7 @@ Set-SPInternalAppStateUpdateInterval -AppStateSyncHours <Int32>
 ```
 
 ## DESCRIPTION
-Use the `Set-SPInternalAppStateUpdateInterval` cmdlet to set the interval in hours between updates of the the internal app state update job.
+Use the `Set-SPInternalAppStateUpdateInterval` cmdlet to set the interval in hours between updates of the internal app state update job.
 The internal app state update job gets app upgrades from the internal app directory and sets them on app instances.
 
 For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at http://go.microsoft.com/fwlink/p/?LinkId=251831 (http://go.microsoft.com/fwlink/p/?LinkId=251831).

sharepoint/sharepoint-ps/sharepoint-server/Set-SPWebApplicationHttpThrottlingMonitor.md

@@ -43,7 +43,7 @@ C:\PS>Set-SPWebApplicationHttpThrottlingMonitor http://sharepoint
 0 -Category Memory -Counter 'Available Mbytes' -IsDesc -UpperLimit 3000
 ```
 
-This example sets the upper limit for the Memory\Available Mbytes counter, the highest value in the Health Score buckets, to 3000 for the the http://sharepoint Web application.
+This example sets the upper limit for the Memory\Available Mbytes counter, the highest value in the Health Score buckets, to 3000 for the http://sharepoint Web application.
 
 
 ## PARAMETERS