Merge branch 'master' into tools

Author: kenwith

exchange/exchange-ps/exchange/policy-and-compliance/New-TransportRule.md

@@ -4484,7 +4484,9 @@ In on-premises Exchange, this action is only available on Mailbox servers.
 
 The RejectMessageEnhancedStatusCode parameter specifies the enhanced status code that's used when the rule rejects messages. Valid values are 5.7.1 or between 5.7.900 and 5.7.999.
 
-You can use this parameter with the NotifySender and RejectMessageReasonText parameters to specify the custom enhanced status code that's used. If you don't use this parameter, the default value 5.7.1 is used.
+You can use this parameter with the NotifySender parameter for a custom non-delivery report (also known as an NDR or bounce message).
+
+If you use this parameter with the RejectMessageReasonText parameter, the enhanced status code value is set to 5.7.1.
 
 To further customize the NDR (for example, multiple languages), you need to create a custom message by using the New-SystemMessage cmdlet.
 
@@ -4507,7 +4509,9 @@ In on-premises Exchange, this action is only available on Mailbox servers.
 
 The RejectMessageReasonText parameter specifies the explanation text that's used when the rule rejects messages. If the value contains spaces, enclose the value in quotation marks (").
 
-You can use this parameter with the NotifySender and RejectMessageEnhancedStatusCode parameters to specify the custom explanation text that's used. If you don't use this parameter, the default value Delivery not authorized, message refused is used.
+You can use this parameter with the NotifySender parameter for a custom non-delivery report (also known as an NDR or bounce message).
+
+If you use this parameter with the RejectMessageEnhancedStatusCode parameter, the custom explanation text value is set to "Delivery not authorized, message refused".
 
 To further customize the NDR (for example, multiple languages), you need to create a custom message by using the New-SystemMessage cmdlet.
 

exchange/exchange-ps/exchange/policy-and-compliance/Set-TransportRule.md

@@ -4479,7 +4479,9 @@ In on-premises Exchange, this action is only available on Mailbox servers.
 
 The RejectMessageEnhancedStatusCode parameter specifies the enhanced status code that's used when the rule rejects messages. Valid values are 5.7.1 or between 5.7.900 and 5.7.999.
 
-You can use this parameter with the NotifySender and RejectMessageReasonText parameters to specify the custom enhanced status code that's used. If you don't use this parameter, the default value 5.7.1 is used.
+You can use this parameter with the NotifySender parameter for a custom non-delivery report (also known as an NDR or bounce message).
+
+If you use this parameter with the RejectMessageReasonText parameter, the enhanced status code value is set to 5.7.1.
 
 To further customize the NDR (for example, multiple languages), you need to create a custom message by using the New-SystemMessage cmdlet.
 
@@ -4502,7 +4504,9 @@ In on-premises Exchange, this action is only available on Mailbox servers.
 
 The RejectMessageReasonText parameter specifies the explanation text that's used when the rule rejects messages. If the value contains spaces, enclose the value in quotation marks (").
 
-You can use this parameter with the NotifySender and RejectMessageEnhancedStatusCode parameters to specify the custom explanation text that's used. If you don't use this parameter, the default value Delivery not authorized, message refused is used.
+You can use this parameter with the NotifySender parameter for a custom non-delivery report (also known as an NDR or bounce message).
+
+If you use this parameter with the RejectMessageEnhancedStatusCode parameter, the custom explanation text value is set to "Delivery not authorized, message refused".
 
 To further customize the NDR (for example, multiple languages), you need to create a custom message by using the New-SystemMessage cmdlet.
 

exchange/exchange-ps/exchange/reporting/Set-UserAnalyticsConfig.md

@@ -79,11 +79,11 @@ Accept wildcard characters: False
 ### -PrivacyMode
 The PrivacyMode parameter specifies the MyAnalytics privacy setting for the user. Valid values are:
 
-- Exclude
+- Excluded
 
-- OptIn
+- Opt-In
 
-- OptOut
+- Opt-Out
 
 ```yaml
 Type: String

officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsExcelUserDefinedFunction.md

@@ -30,7 +30,7 @@ New-OfficeWebAppsExcelUserDefinedFunction -Assembly c:\myudf.dll -AssemblyLocati
 
 ### ------------------EXAMPLE 2---------------------
 ```
-New-OfficeWebAppsExcelUserDefinedFunction -Assembly "CompanyName.Hierarchichal.MyUdfNamespace.MyUdfClassName.dll, Version=1.1.0.0, Culture=en, PublicKeyToken=e8123117d7ba9ae38" -AssemblyLocation GAC -Enable:$true -Description "My GAC Server UDFs"
+New-OfficeWebAppsExcelUserDefinedFunction -Assembly "CompanyName.Hierarchical.MyUdfNamespace.MyUdfClassName.dll, Version=1.1.0.0, Culture=en, PublicKeyToken=e8123117d7ba9ae38" -AssemblyLocation GAC -Enable:$true -Description "My GAC Server UDFs"
 ```
 
 ## PARAMETERS

officewebapps/officewebapps-ps/officewebapps/New-OfficeWebAppsFarm.md

@@ -368,7 +368,7 @@ Accept wildcard characters: False
 ```
 
 ### -ExcelExternalDataCacheLifetime
-Specifes the duration, in seconds, of the external data cache lifetime in Excel Online.
+Specifies the duration, in seconds, of the external data cache lifetime in Excel Online.
 The default is 300 seconds.
 
 ```yaml
@@ -760,7 +760,7 @@ Accept wildcard characters: False
 Turns on or off the ability to use Online Viewers to view Office files from a URL or UNC path.
 The default is False.
 
-You must set this paramater to True when you use ClipartEnabled.
+You must set this parameter to True when you use ClipartEnabled.
 
 ```yaml
 Type: SwitchParameter

repo_docs/UPDATE_CMDLETS.md

@@ -3,19 +3,19 @@ Manually adding new parameters to a cmdlet reference topic is doable, but there
 
 - **Add the paramter and Type value to the SYNTAX block(s)**: Easy to do if there's only one, but what if there are multiple SYNTAX blocks (also known as parameter sets)? Does the new parameter go in one, some, or all of them? And what about the parameter Type value (String? `$true | $ false`? A finite list of values?)
 
-- **Create a new section for each parameter**: It's easy to create the section and write the descrition, but again, what about the parameter Type value? And which parameter sets does it belong to?
+- **Create a new section for each parameter**: It's easy to create the section and write the description, but again, what about the parameter Type value? And which parameter sets does it belong to?
 
 The reality is: you almost always need the open-source [platyPS](https://github.com/PowerShell/platyPS) tool to automatically answer the unknowns about new parameters.
 
-Currently, the best method with platyPS is to simply create a new version of the topic using the **New-MarkdownHelp** cmdlet, and copy whatever you need out of it. Theoretically, platyPS has an **Update-MarkdownHelp** cmdlet that automatically updates an existing local copy of the topic for you, which you can then upload in its entirety to the GitHub website to replace the exisitng topic. This approach currently has some issues in our enviornment:
+Currently, the best method with platyPS is to simply create a new version of the topic using the **New-MarkdownHelp** cmdlet, and copy whatever you need out of it. Theoretically, platyPS has an **Update-MarkdownHelp** cmdlet that automatically updates an existing local copy of the topic for you, which you can then upload in its entirety to the GitHub website to replace the existing topic. This approach currently has some issues in our environment:
 
 - It's difficult to get a local copy of an existing cmdlet topic from the GitHub website (unless you're interested in forking the repo and having a local cloned copy on your computer). You have to copy/paste everything from the Raw view of the topic on the web site, and the local copy text file you manually create needs to be UTF-8 formatted (instead of the Notepad default of ANSI).
 
 - The updated topic will have missing or incorrect _unrelated_ parameter and other topic metadata information that you'll need to change by copy/pasting those values _back from_ the existing topic on GitHub into your local topic before you can even think about uploading the updated topic to GitHub (more than double the work required).
 
 In short, it's simply easier and faster to generate a new local copy of the cmdlet topic, and copy/paste only what you need into the existing topic on GitHub.
 
-Removing parameters from topics is a manual excercise, but we'll explain the process fully.
+Removing parameters from topics is a manual exercise, but we'll explain the process fully.
 
 ## Use platyPS to add new cmdlets to existing topics
 
@@ -28,7 +28,7 @@ You probably know how to do this already, but the available workloads and connec
 ### Step 3: Load platyPS in the PowerShell environment
 After you've connected in PowerShell to the server or service (either in a regular Windows PowerShell window or from a specific PowerShell console shortcut), run the following command to make the platyPS cmdlets available in your session:
 
-```
+```powershell
 Import-Module platyPS
 ```
 
@@ -39,37 +39,37 @@ To recap: this step is required in Exchange, Skype for Business Online and other
 
 If you're using SharePoint, SharePoint Online or another product that doesn't use remote PowerShell to connect, you can skip this step.
 
-### Step 5: Use New-MarkdownHelp to dump the latest verion of the cmdlet to a file
+### Step 5: Use New-MarkdownHelp to dump the latest version of the cmdlet to a file
 These instructions are the same (up to a point) as in [Create new cmdlet topics](NEW_CMDLETS.md):
 
 The basic syntax is:
 
- ```
+ ```powershell
  New-MarkdownHelp -Command <Cmdlet> -OutputFolder "<Path"> [-Session <PSSessionVariableName>]
  ``` 
 
  or 
 
- ```
+ ```powershell
  $x = "<Cmdlet1>","<Cmdlet2>",..."<CmdletN>"
  New-MarkdownHelp -Command $x -OutputFolder "<Path"> [-Session <PSSessionVariableName>]
  ``` 
 
  This example create a topic file for the updated cmdlet named Get-CoolFeature in the Exchange Online PowerShell session where the session variable is `$Session` in the folder "C:\My Docs\ExO".
 
-```
+```powershell
 New-MarkdownHelp -Command "Get-CoolFeature" -OutputFolder "C:\My Docs\ExO" -Session $Session
 ```
 
 This example creates topic files for the updated cmdlets Get-CoolFeature, New-CoolFeature, Remove-CoolFeature, and Set-CoolFeature from the Exchange Online session where the session variable is `$Session` in the folder C:\My Docs\ExO. 
 
 The first command stores the cmdlet names in a variable. The second command uses that variable to identify the cmdlets and write the output files.
 
-```
+```powershell
 $Delta = "Get-CoolFeature","New-CoolFeature","Remove-CoolFeature","Set-CoolFeature"
 ```
 
-```
+```powershell
 New-MarkdownHelp -Command $Delta -OutputFolder "C:\My Docs\ExO" -Session $Session
 ```
 
@@ -78,25 +78,25 @@ The resulting topics are plain text UTF-8 files that are formatted using [markdo
 
 1. Find the new parameter(s) in the SYNTAX block and the parameter sections.
 
-2. Add a parameter description. We highly enourage you to plagerize existing content and formatting from other cmdlet topics. Many parameters are common across a wide variety of cmdlets. 
+2. Add a parameter description. We highly encourage you to plagiarize existing content and formatting from other cmdlet topics. Many parameters are common across a wide variety of cmdlets. 
 
 3. Create/fill out the parameter metadata like other existing parameters in the topic.
 
     Here's an example of the parameter metadata that's present in every parameter section:
 
-        ```
-        Type: String
-        Parameter Sets: (All)
-        Aliases:
-        Applicable: Microsoft StaffHub
-        Required: False
-        Position: 1
-        Default value: None
-        Accept pipeline input: False
-        Accept wildcard characters: False
+    ```yaml
+    Type: String
+    Parameter Sets: (All)
+    Aliases:
+    Applicable: Microsoft StaffHub
+    Required: False
+    Position: 1
+    Default value: None
+    Accept pipeline input: False
+    Accept wildcard characters: False
     ```
 
-  Most of the atrributes and values are generated automatically by platyPS. The ones that require manual intervention are:
+  Most of the attributes and values are generated automatically by platyPS. The ones that require manual intervention are:
 
   - **Applicable**: You need to add this attribute and value yourself. Notice the capital 'A'. See other topics for available values (same available values as the **applicable** attribute at the top of the topic). Don't invent new values here. The value **must** come from the list of predefined values.
 
@@ -109,7 +109,7 @@ At this point, the steps are basically identical to [Short URL: aka.ms/office-po
 
     - Exchange: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/exchange/exchange-ps/exchange](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/exchange/exchange-ps/exchange)
 
-       For Exchage, you also need to go one level deepter into an appropriate subfolder.
+       For Exchange, you also need to go one level deeper into an appropriate subfolder.
 
     - Office Web Apps: [https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/officewebapps/officewebapps-ps/officewebapps](https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/officewebapps/officewebapps-ps/officewebapps)
 
@@ -141,9 +141,9 @@ At this point, the steps are basically identical to [Short URL: aka.ms/office-po
 7. On the next screen, click **Create pull request**.
 
 ## Remove existing parameters from existing topics
-Removing parameters is a search and destroy mission in the existing topics on GitHub, using the basic [Editing Instrucstions](../README.md).
+Removing parameters is a search and destroy mission in the existing topics on GitHub, using the basic [Editing Instructions](../README.md).
 
-The most important thing to remember: a parameter isn't gone until it's truly not available to customers. If a parameter is still available, but it's going away "in the future", it doesn't work correctly anymore, or isn't supposed to be available, it needs to remain in the topic until the product code is actually changed to remove the parameter. Until then, you can use this type of languague for the parameter description:
+The most important thing to remember: a parameter isn't gone until it's truly not available to customers. If a parameter is still available, but it's going away "in the future", it doesn't work correctly anymore, or isn't supposed to be available, it needs to remain in the topic until the product code is actually changed to remove the parameter. Until then, you can use this type of language for the parameter description:
 
 - This parameter is reserved for internal Microsoft use.
 

sharepoint/sharepoint-ps/sharepoint-online/ConvertTo-SPOMigrationEncryptedPackage.md

@@ -8,7 +8,7 @@ schema: 2.0.0
 # ConvertTo-SPOMigrationEncryptedPackage
 
 ## SYNOPSIS
-Use this Cmdlet to convert your XML files into a new encryted migration package.
+Use this Cmdlet to convert your XML files into a new encrypted migration package.
 
 ## SYNTAX
 
@@ -27,7 +27,7 @@ ConvertTo-SPOMigrationEncryptedPackage -EncryptionParameters <EncryptionParamete
 ```
 
 ## DESCRIPTION
-This command convert the XML file on your temprary XML folder files into a new set of targeted migration encrypted metadata files to the target directory.
+This command convert the XML file on your temporary XML folder files into a new set of targeted migration encrypted metadata files to the target directory.
 
 ## EXAMPLES
 
@@ -47,12 +47,12 @@ PS C:\> ConvertTo-SPOMigrationEncryptedPackage -EncryptionParameters SHA384
  -TargetPackagePath $TargetPackagePath
 ```
 
-Same as example1 but without log file and using an encription type SHA384
+Same as example1 but without log file and using an encryption type SHA384
 
 ## PARAMETERS
 
 ### -EncryptionParameters
-Parameters of the encription, it doesn't accept wildcard caracters.
+Parameters of the encryption, it doesn't accept wildcard characters.
 It accepts parameters like SHA384, SHA256, etc.
 
 ```yaml
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 ```
 
 ### -MigrationSourceLocations
-Posible Source locations to migrate
+Possible Source locations to migrate
 
 ```yaml
 Type: MigrationPackageLocation

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.md

@@ -8,7 +8,7 @@ schema: 2.0.0
 # Get-SPOGeoAdministrator
 
 ## SYNOPSIS
-This cmdlet returns the SharePoint Online user or security group accounts with global administrative privilegies in the current Multi-Geographics tenant
+This cmdlet returns the SharePoint Online user or security group accounts with global administrative privileges in the current Multi-Geographics tenant
 
 ## SYNTAX
 

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserAndContentMoveState.md

@@ -51,7 +51,7 @@ Obtain the move state by OneDrive Move Job ID
 ### Example 2
 
 ```Powershell
-Get-SPOUserAndContentMoveState -movestate NotStarted
+Get-SPOUserAndContentMoveState -MoveState NotStarted
 ```
 Getting which moves are being done in a particular state
 ###Example 3

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOGeoAdministrator.md

@@ -22,7 +22,7 @@ This cmdlet contains a single parameter set.
 You may only use parameters from one parameter set and you may not combine parameters from different parameter sets.
 For more information about how to use parameter sets, see Cmdlet Parameter Sets (http://go.microsoft.com/fwlink/?LinkID=187810).
 
-The `Remove-SPOGeoAdministrator` cmdlet matches a user or a security group and remove the GeoAdministrator privilegies in the SharePoint Organization.
+The `Remove-SPOGeoAdministrator` cmdlet matches a user or a security group and remove the GeoAdministrator privileges in the SharePoint Organization.
 
 You must be a SharePoint Online global administrator and you must have a Multi-Geo Tenant to run the `Get-SPOGeoAdministrator` cmdlet.
 
@@ -37,7 +37,7 @@ For permissions and the most current information about Windows PowerShell for Sh
 ```powershell
 Remove-SPOGeoAdministrator contosoadmin [-LoginName] <String>
 ```
-Remove the GeoAdministrator privilegies to the user contosoadmin of the SharePoint Online multi-geo tenant.
+Remove the GeoAdministrator privileges to the user contosoadmin of the SharePoint Online multi-geo tenant.
 
 ### Example 2
 ```powershell

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOPublicCdnOrigin.md

@@ -58,7 +58,7 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-It's the unique identificator of the Public CDN path, it can be queried using the Cmdlet Get-SpoPublicCdnOrigins
+It's the unique identifier of the Public CDN path, it can be queried using the Cmdlet Get-SpoPublicCdnOrigins
 
 ```yaml
 Type: String

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantCdnOrigin.md

@@ -25,14 +25,14 @@ Removes a new origin from the Public or Private content delivery network (CDN).
 ## EXAMPLES
 
 ### -----------------------EXAMPLE 1-----------------------------
-```
+```powershell
 Remove-SPOTenantCdnOrigin -CdnType Public -OriginUrl sites/pubsite/siteassets/subfolder
 ```
 
 The example removes a CDN from a tenant level.
 
 ### -----------------------EXAMPLE 2-----------------------------
-```
+```powershell
 Remove-SPOTenantCdnOrigin -CdnType Public -OriginScope Site  -Site https://contoso.sharepoint.com/sites/pubsite -OriginUrl siteassets/subfolder
 ```
 
@@ -42,7 +42,7 @@ The example removes a CDN from a site level.
 ## PARAMETERS
 
 ### -CdnType
-Specifies the CDN type. The valuid values are: Public or Private.
+Specifies the CDN type. The valid values are: Public or Private.
 
 
 ```yaml
@@ -82,7 +82,7 @@ Relative-Relative path depends on the OriginScope. If the originScope is Tenant,
 
 Any asset stored under the path provided (in the container itself or any of its subfolders) will be exposed via CDN
 
-Mask - Mask allows to configure a partial URL match. It must start with */, and must not include * anywhere else. I.e. an origin “*/masterpates” will expose all the assets under all the masterpages libraries, either under the tenant root (means, anywhere in the tenancy) or in the given site collection, depends on the OriginScope parameter. Equally, */masterpages/subfolder will enable items in “subfolder” and below.
+Mask - Mask allows to configure a partial URL match. It must start with */, and must not include * anywhere else. I.e. an origin “*/masterpages” will expose all the assets under all the masterpages libraries, either under the tenant root (means, anywhere in the tenancy) or in the given site collection, depends on the OriginScope parameter. Equally, */masterpages/subfolder will enable items in “subfolder” and below.
 
 
 ```yaml