Merge pull request MicrosoftDocs#260 from tseward/patch-38

Update Copy-SPContentTypes.md

Author: Techwriter40

sharepoint/sharepoint-ps/sharepoint-server/Copy-SPContentTypes.md

@@ -1,14 +1,14 @@
 ---
 external help file: 
-applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+applicable: SharePoint Server 2013, SharePoint Server 2016
 title: Copy-SPContentTypes
 schema: 2.0.0
 ---
 
 # Copy-SPContentTypes
 
 ## SYNOPSIS
-{{Fill in the Synopsis}}
+Specifies content types for replicating from on-premises to SharePoint Online (SPO) environment.
 
 ## SYNTAX
 
@@ -19,27 +19,29 @@ Copy-SPContentTypes [-AssignmentCollection <SPAssignmentCollection>] [-AuthEndpo
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+This cmdlet is used in hybrid scenarios with SharePoint Online to copy Content Types from an on-premises farm to SharePoint Online.
 
 ## EXAMPLES
 
 ### Example 1 
 ```
-PS C:\> {{ Add example code here }}
+PS C:\>Copy-SPContentTypes -LocalSiteUrl http://localsite/ -LocalTermStoreName "managed metadata service application proxy" -RemoteSiteUrl https://contoso.sharepoint.com/ -ContentTypeNames @("ContentTypeA", "ContentTypeB") -Credential (Get-Credential) 
 ```
 
-{{ Add example description here }}
+This example migrates the specified content types named: ContentTypeA, ContentTypeB on the local site http://localsite/ whose term store named "managed metadata service application proxy" to the hub site of remote site https://contoso.sharepoint.com/. If the remote site is a hub site, the migration target will be itself. 
 
 ## PARAMETERS
 
 ### -AssignmentCollection
-{{Fill AssignmentCollection Description}}
+Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
+
+**NOTE**: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
 
 ```yaml
 Type: SPAssignmentCollection
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: False
 Position: Named
@@ -49,13 +51,13 @@ Accept wildcard characters: False
 ```
 
 ### -AuthEndpoint
-{{Fill AuthEndpoint Description}}
+Specifies the AuthEndpoint to use, but not the default one.
 
 ```yaml
 Type: String
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: False
 Position: Named
@@ -65,13 +67,13 @@ Accept wildcard characters: False
 ```
 
 ### -ContentTypeNames
-{{Fill ContentTypeNames Description}}
+Specifies the content type names to be migrated. Can be in a form of an array. 
 
 ```yaml
 Type: String[]
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: True
 Position: Named
@@ -81,13 +83,13 @@ Accept wildcard characters: False
 ```
 
 ### -Credential
-{{Fill Credential Description}}
+Specifies the administrator account credential of the target SharePoint Online site.
 
 ```yaml
 Type: PSCredential
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: True
 Position: Named
@@ -97,13 +99,13 @@ Accept wildcard characters: False
 ```
 
 ### -GraphApiEndPoint
-{{Fill GraphApiEndPoint Description}}
+Specifies the GraphApiEndpoint to use, but not the default one.
 
 ```yaml
 Type: String
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: False
 Position: Named
@@ -113,13 +115,13 @@ Accept wildcard characters: False
 ```
 
 ### -LocalSiteUrl
-{{Fill LocalSiteUrl Description}}
+Specifies the migration source. Can be a local site or a local hubsite.
 
 ```yaml
 Type: Uri
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: True
 Position: Named
@@ -129,13 +131,13 @@ Accept wildcard characters: False
 ```
 
 ### -LocalTermStoreName
-{{Fill LocalTermStoreName Description}}
+Specifies the name of the local term store of the local site.
 
 ```yaml
 Type: String
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: True
 Position: Named
@@ -145,13 +147,13 @@ Accept wildcard characters: False
 ```
 
 ### -RemoteSiteUrl
-{{Fill RemoteSiteUrl Description}}
+Specifies the migration target. You can input a remote site url or remote hub site url, both will be processed to be the hub site url.
 
 ```yaml
 Type: Uri
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: True
 Position: Named