Merge branch 'master' into patch-244

Author: Kateyanne

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

@@ -109,6 +109,14 @@ Get-SPOSite -Identity https://contoso.sharepoint.com/sites/research | Select Inf
 
 This example returns the InformationSegments associated to the site.
 
+### -----------------------EXAMPLE 7-----------------------------
+
+```powershell
+Get-SPOSite -Filter { Url -like "contoso.sharepoint.com/sites/18" }
+```
+
+This example uses server side filtering to return sites matching 18.
+
 ## PARAMETERS
 
 ### -Detailed
@@ -170,7 +178,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-Specifies the script block of the server-side filter to apply. The type must be a valid filter name and value must be in the form `{$_PropertyName <operator> "filterValue"}`. Valid operators are as follows: eq, ne, like, notlike.
+Specifies the script block of the server-side filter to apply. The type must be a valid filter name and value must be in the form `{ PropertyName <operator> "filterValue"}`. Valid operators are as follows: -eq, -ne, -like, -notlike.
  Currently, you can filter by these properties: Owner, Template, LockState, Url.
 
 > [!NOTE]

sharepoint/sharepoint-ps/sharepoint-server/Mount-SPContentDatabase.md

@@ -16,6 +16,7 @@ ms.reviewer:
 
 Attaches an existing content database to the farm.
 
+NOTE: Please be aware that if a content database that does not exists is specified, it will be created by this cmdlet.
 
 
 ## SYNTAX
@@ -32,6 +33,7 @@ Mount-SPContentDatabase [-Name] <String> [-WebApplication] <SPWebApplicationPipe
 ## DESCRIPTION
 The Mount-SPContentDatabase cmdlet attaches an existing content database to the farm.
 If the database being mounted requires an upgrade, this cmdlet will cause the database to be upgraded.
+NOTE: Please be aware that if a content database that does not exists is specified, it will be created by this cmdlet.
 
 The default behavior of this cmdlet causes an upgrade of the schema of the database and initiates upgraded builds for all site collections within the specified content database if required.
 To prevent initiation of upgraded builds of site collections, use the NoB2BSiteUpgrade parameter.
@@ -401,4 +403,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## NOTES
 
 ## RELATED LINKS
-

skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md

@@ -22,7 +22,7 @@ Grant-CsTeamsUpgradePolicy [-Identity] <UserIdParameter>] [-PolicyName] <string>
 ```
 
 ## DESCRIPTION
-TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. As an organization with Skype for Business starts to adopt Teams, administrators can manage the user experience in their organization using the concept of coexistence "mode".  Mode defines in which client incoming chats and calls land as well as in what service (Teams or Skype for Business) new meetings are scheduled in. Mode also governs what functionality is avaiable in the Teams client.  Finally, prior to upgrading to TeamsOnly mode administrators can use TeamsUpgradePolicy to trigger notifications in the Skype for Business client to inform users of the pending upgrade. 
+TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. As an organization with Skype for Business starts to adopt Teams, administrators can manage the user experience in their organization using the concept of coexistence "mode".  Mode defines in which client incoming chats and calls land as well as in what service (Teams or Skype for Business) new meetings are scheduled in. Mode also governs what functionality is available in the Teams client. Finally, prior to upgrading to TeamsOnly mode administrators can use TeamsUpgradePolicy to trigger notifications in the Skype for Business client to inform users of the pending upgrade. 
 
 This cmdlet enables admins to apply TeamsUpgradePolicy to either individual users or to set the default for the entire organization.