Merge pull request MicrosoftDocs#2206 from greiginsydney/patch-8

Minor typo and MD formatting corrections.

Author: kenwith

skype/skype-ps/skype/Grant-CsTeamsInteropPolicy.md

@@ -23,15 +23,13 @@ Grant-CsTeamsInteropPolicy [-PassThru] [-Confirm] [[-PolicyName] <Object>] [[-Id
 
 ## DESCRIPTION
 
-IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. It is no longer honored by the system, except if TeamsUpgradePolicy has mode=Lgeacy.  Legacy mode is being deprecated. Customers that are still using Legacy mode should update their configurations to use a mode other than Legacy.  Granting mode=Legacy is now blocked by default, although admins can override this using -Force for the time being. Eventually, the -Force switch will be removed and granting mode=Legacy will not be possible.
+IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. It is no longer honored by the system, except if TeamsUpgradePolicy has mode=Legacy.  Legacy mode is being deprecated. Customers that are still using Legacy mode should update their configurations to use a mode other than Legacy.  Granting mode=Legacy is now blocked by default, although admins can override this using -Force for the time being. Eventually, the -Force switch will be removed and granting mode=Legacy will not be possible.
 
 Any customers still using Legacy mode must ensure the following:
- - The global policy must have CallingDefaultClient=ChatDefaultClient, and AllowEndUserClientOverride must be false.  If you customized the built-in global policy, undo this by running `Remove-CsTeamsInteropPolicy`. This will remove the tenant-specific global policy and revert back to the system-wide built-in policy (which cannot be removed). Use the following syntax:
- 
-Remove-CsTeamsInteropPolicy -Identity Global
 
- - If TeamsInteropPolicy is explicitly assigned to any users, one of these three built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are no longer valid configurations, are  not supported, and will soon be removed from the system.  The valid instances are:
+ - The global policy must have CallingDefaultClient=ChatDefaultClient, and AllowEndUserClientOverride must be false.  If you customized the built-in global policy, undo this by running `Remove-CsTeamsInteropPolicy`. This will remove the tenant-specific global policy and revert back to the system-wide built-in policy (which cannot be removed). Use the following syntax: `Remove-CsTeamsInteropPolicy -Identity Global`.
 
+ - If TeamsInteropPolicy is explicitly assigned to any users, one of these three built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are no longer valid configurations, are not supported, and will soon be removed from the system.  The valid instances are:
 
 **Identity: DisallowOverrideCallingDefaultChatDefault**   
 **AllowEndUserClientOverride: False**   
@@ -48,10 +46,7 @@ Remove-CsTeamsInteropPolicy -Identity Global
 **CallingDefaultClient: Teams**     
 **ChatDefaultClient: Teams**
 
-
-Use the following cmdlet syntax, where $policy is one of the above values of identity:
-`Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`
-
+Use the following cmdlet syntax, where $policy is one of the above values of identity: `Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`.
 
 For comprehensive documentation on this policy and its settings, see [Microsoft Teams and Skype for Business Interoperability](https://docs.microsoft.com/MicrosoftTeams/teams-and-skypeforbusiness-interoperability).
 
@@ -112,7 +107,7 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-For this cmdlet, the full UserPrincipleName/SIP address is required. If you don't provide the full UPN/SIP and instead provide an Alias, the cmdlet can throw an "Object reference not set to an instance of an object" error.
+For this cmdlet, the full UserPrincipalName/SIP address is required. If you don't provide the full UPN/SIP and instead provide an Alias, the cmdlet can throw an "Object reference not set to an instance of an object" error.
 
 ```yaml
 Type: Object
@@ -217,7 +212,7 @@ Accept wildcard characters: False
 ### System.Object
 
 ## NOTES
-This policy has been deprecated. Customters should use TeamsUpgradePolicy to control interop and routing.
+This policy has been deprecated. Customers should use TeamsUpgradePolicy to control interop and routing.
 
 ## RELATED LINKS