Update Disable-CsOnlineSipDomain.md

fit n finish fixes after David's review

Author: bjwhalen

skype/skype-ps/skype/Disable-CsOnlineSipDomain.md

@@ -14,21 +14,20 @@ This cmdlet prevents provisioning of users in Skype for Business Online for the
 ## SYNTAX
 
 ```
-Disable-CsOnlineSipDomain -Domain <String> [-Tenant <System.Guid>] [-DomainController <String>] [-Force]
- [-WhatIf] [-Confirm] [<CommonParameters>]
+Disable-CsOnlineSipDomain -Domain <String> [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
 This cmdlet enables organizations with *multiple on-premises deployments of Skype for Business Server (or Lync Server)* to safely synchronize users from multiple forests into a single Office 365 tenant.  When an an online SIP domain is disabled in Skype for Business Online, provisioning is blocked for users in this SIP domain. This ensures routing for any on-premises users in this SIP domain continues to function properly.
 
 This cmdlet facilitates consolidation of multiple Skype for Business Server deployments into a single Office 365 tenant. Consolidation can be achieved by moving one deployment at a time into Office 365, **provided the following key requirements are met**:
  - There must be at most 1 O365 tenant involved. Consolidation in scenarios with >1 O365 tenant is not supported.
- - At any given time, only 1 on-premise SfB forest can be in hybrid mode (shared sip address space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably federated with each other.)  
+ - At any given time, only 1 on-premise SfB forest can be in hybrid mode (Shared Sip Address Space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably are federated with each other.)  
  - If 1 deployment is in hybrid mode, all sip domains from any other SfB forests must be disabled using this cmdlet before they can be synchronized into the tenant with Azure AD Connect. Users in all SfB forests other than the hybrid forest must remain on-premises.
   - Organizations must fully migrate each SfB forest individually into the O365 tenant using hybrid mode (Shared Sip Address Space), and then detach the “hybrid” deployment, *before* moving on to migrate the next on-premise SfB deployment.   
 
 
-This cmdlet may also be useful for organizations with on-premises deployments of Skype for Business Server that have not properly configured Azure AD Connect. If the organization does not sync msRTCSIP-DeploymentLocator for its users, then Skype for Business Online will attempt to provision users online, despite there being users on-premises.  While the correct fix is to update the configuration for Azure AD Connect to sync those attributes, using Disable-CsOnlineSipDomain can also mitigate the problem until that configuration change can be made.  If this cmdlet is run, any users that were previously provisioned online in that domain will be de-provisioned in Skype for Business Online.
+This cmdlet may also be useful for organizations with on-premises deployments of Skype for Business Server that have not properly configured Azure AD Connect. If the organization does not sync msRTCSIP-DeploymentLocator for its users, then Skype for Business Online will attempt to provision online any users with an assigned Skype for Business license, despite there being users on-premises.  While the correct fix is to update the configuration for Azure AD Connect to sync those attributes, using Disable-CsOnlineSipDomain can also mitigate the problem until that configuration change can be made.  If this cmdlet is run, any users that were previously provisioned online in that domain will be de-provisioned in Skype for Business Online.
 
 **IMPORTANT**
 This cmdlet should not be run for domains that contain users hosted in Skype for Business Online.  Any users in a sip domain that are already provisioned *online* will cease to function if you disable the online sip domain:
@@ -45,12 +44,12 @@ This cmdlet should not be run for domains that contain users hosted in Skype for
 PS C:\> Disable-CsOnlineSipDomain -Domain  Fabrikam.com
 ```
 
-The cmdlet above disables the online sip domain Fabrikam.com.  This would be useful in the case where a company, Contoson.com, that  has Skype for Business acquires Fabkrikam, which also has an on-premises deployment of Skype for Business Server.  If Contoso is in hybrid mode with Skype for Business Online. or if the intent is to configure it for hybrid, then if the organization wants to synchroize identities from Fabrikam.com into the same O365 tenant, the organization must first run this cmdlet.
+The cmdlet above disables the online sip domain Fabrikam.com.  This would be useful in the case where a company, Contoso.com, that  has Skype for Business acquires Fabrikam, which also has an on-premises deployment of Skype for Business Server.  If Contoso is in hybrid mode with Skype for Business Online or if the intent is to configure it for hybrid, then if the organization wants to synchronize identities from Fabrikam.com into the same O365 tenant, the organization must first run this cmdlet.
 
 ## PARAMETERS
 
 ### -Domain
-{{Fill Domain Description}}
+The SIP domain to be disabled for online provisioning in Skype for Business Online.
 
 ```yaml
 Type: String
@@ -80,7 +79,7 @@ Accept wildcard characters: False
 ```
 
 ### -Force
-{{Fill Force Description}}
+Suppresses all confirmation prompts that might occur when running the command.
 
 ```yaml
 Type: SwitchParameter
@@ -94,20 +93,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Tenant
-{{Fill Tenant Description}}
-
-```yaml
-Type: System.Guid
-Parameter Sets: (All)
-Aliases:
-applicable: Skype for Business Online
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
 
 ### -WhatIf
 Shows what would happen if the cmdlet runs.
@@ -135,6 +120,8 @@ For more information, see about_CommonParameters (http://go.microsoft.com/fwlink
 
 ## OUTPUTS
 
+### None
+
 ### System.Object
 ## NOTES
 This cmdlet is for advanced scenarios only.  Organizations that are pure online or have only 1 on-premise deployment need not run this cmdlet.