initial changes

Author: AmareshB1Microsoft

exchange/exchange-ps/exchange/reporting/Get-LicenseVsUsageSummaryReport.md

@@ -33,7 +33,7 @@ This cmdlet produces a report that is intended to enable clients to track and ma
 
 - TenantGuid: The unique identifier for the Exchange Online tenant.
 
-- Workload: The workload whose users are being counted. The current workloads include: Exchange Online, SharePoint Online, Skype for Business Online, and Microsoft Yammer.
+- Workload: The workload whose users are being counted. The current workloads include: Exchange Online, SharePoint Online, and Microsoft Yammer.
 
 - NonTrialEntitlements: The number of entitled users for the workload.
 

repo_docs/NEW_CMDLETS.md

@@ -105,7 +105,7 @@ For SharePoint Online in the SharePoint Online Management Shell, the module name
 Either way, take note of your module name. You'll need it in the next steps.
 
 ### Step 5: Verify your PSSession variable name
-**Note**: This step is required in Exchange, Skype for Business Online and other products that use remote PowerShell in their connection instructions (one or more **xxx-xxxSession** commands are present). **If you're using SharePoint, SharePoint Online or another product that doesn't use remote PowerShell, you can skip this step**.
+**Note**: This step is required in Exchange and other products that use remote PowerShell in their connection instructions (one or more **xxx-xxxSession** commands are present). **If you're using SharePoint, SharePoint Online or another product that doesn't use remote PowerShell, you can skip this step**.
 
 Check the details of your connection instructions, but your session information is stored in a variable. For example, in the Exchange connection instructions, the variable is `$Session`. You'll use this variable name in later steps.
 

repo_docs/UPDATE_CMDLETS.md

@@ -35,7 +35,7 @@ Import-Module platyPS
 ### Step 4: Verify your PSSession variable name
 This step is the same as in [Create new cmdlet topics](NEW_CMDLETS.md#step-5-verify-your-your-pssession-variable-name).
 
-To recap: this step is required in Exchange, Skype for Business Online and other products that use remote PowerShell in their connection instructions (one or more **xxx-xxxSession** commands are present), and the value is most likely `$Session`.
+To recap: this step is required in Exchange and other products that use remote PowerShell in their connection instructions (one or more **xxx-xxxSession** commands are present), and the value is most likely `$Session`.
 
 If you're using SharePoint, SharePoint Online or another product that doesn't use remote PowerShell to connect, you can skip this step.
 

skype/docs-conceptual/index.md

@@ -5,11 +5,11 @@ title: Skype for Business cmdlet reference
 
 # Skype for Business cmdlet reference
 
-Welcome to the Skype for Business PowerShell cmdlet help references. The Skype for Business cmdlets provide the command line interface for server and service administration and management.
+Welcome to the Skype for Business PowerShell cmdlet help references. The Skype for Business cmdlets provide the command line interface for server administration and management.
 
 > [!IMPORTANT]
-> As you migrate to Microsoft Teams you will find that some of the cmdlets in the Skype for Business Online module are also used for Microsoft Teams. To learn more about this, see: [Teams PowerShell Overview](https://docs.microsoft.com/MicrosoftTeams/teams-powershell-overview).
+> For administration of Microsoft Teams, see: [Teams PowerShell Overview](https://docs.microsoft.com/MicrosoftTeams/teams-powershell-overview).
 
-Here you will find all of the Skype for Business and relevant Microsoft Teams PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. 
+Here you will find all of the Skype for Business help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. 
 
 The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page.

skype/docs-conceptual/intro.md

@@ -5,11 +5,11 @@ title: Skype for Business cmdlet reference
 
 # Skype for Business cmdlet reference
 
-Welcome to the Skype for Business PowerShell cmdlet help references. The Skype for Business cmdlets provide the command line interface for server and service administration and management.
+Welcome to the Skype for Business PowerShell cmdlet help references. The Skype for Business cmdlets provide the command line interface for server administration and management.
 
 > [!IMPORTANT]
-> As you migrate to Microsoft Teams you will find that some of the cmdlets in the Skype for Business Online module are also used for Microsoft Teams. To learn more about this, see: [Teams PowerShell Overview](https://docs.microsoft.com/MicrosoftTeams/teams-powershell-overview).
+> For administration of Microsoft Teams, see: [Teams PowerShell Overview](https://docs.microsoft.com/MicrosoftTeams/teams-powershell-overview).
 
-Here you will find all of the Skype for Business and relevant Microsoft Teams PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. 
+Here you will find all of the Skype for Business help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. 
 
 The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page.